Accidentally nuked anything libgd* - where to begin the restoration?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Accidentally nuked anything libgd* - where to begin the restoration?
Hi:
I was following a document to load some libraries for a GIS internet mapping app called Mapserver. Part of the doc called for "cleaning up" the libgd libraries. Problem is, I executed a rm -f /usr/lib/libgd* when it should have been libgd.*
Well, I cam caught in the deadly "INIT:ID "X" Respawing too fast" cycle.
Yeah, you blew away the GD graphics library and the GDBM database library. Looks like your desktop needs them. :-) Boot it to runlevel 3 instead of 5 and use it in text mode. From there you can use rpm to assess the damage. Probably just forcing a re-install of the "gd" and "gdbm" packages would fix things. I'm not sure why your app's docs said to remove the GD libraries, that doesn't sound like a good idea to me.
BTW: you can find out if files are owned by any installed package by using a pipe such as this one:
/bin/ls /usr/lib/libgd* | xargs -n 1 rpm -qf | sort -u
If there's any output, then you know that you shouldn't remove those files because something else depends on them. I know, that won't prevent accidents like yours, but maybe it will help you down the road.
Yep, thanks for that. Still learning. Got it back up by forcing the GD back in. Not sure what you meant by using RPM to assess the damage. a Rehat RPM?
That command will come in handy. I need to know about dependencies. Do you know of a good Linux book that tells how to do all the command line stuff to check for dependencies, how to load and manage libraries etc?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.