LinuxQuestions.org - freezes loading name server cache daemon

- SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)

- - freezes loading name server cache daemon (https://www.linuxquestions.org/questions/suse-opensuse-60/freezes-loading-name-server-cache-daemon-261076/)

freezes loading name server cache daemon

Distro is Suse 9.1 - everything was working fine (for weeks)... booted into win2k and it worked as well as windows ever does, then I restarted to boot back into Suse and it freezes loading "Name Server Cache Daemon". Tried restarting, tried booting into "Failsafe" and it still freezes. What could be causing this and is there a workaround/fix?
Thanks a lot!
Billy :newbie:

personally i'd say kill that service... it's just a crippled version of bind which might speed u pyour dns hits by .25 seconds sometimes... as for the problem... maybe a lockfile or somethign like that, but also it might be a netowrknig thing. have you tried leaving it to timeout for a length of time? either way i'd suggest just cutting it out for now, by deleting /etc/rc5.d/S80dnscache or whatever it's going to be called on suse. this is only a symlink to the real service, so totally replacable at any point you want to. (and rc5.d is assuming you boot to X, if you use a console login, change the 5 to a 3.) if you're having a hard time getting in at all, try booting to single user mode, add a "1" or "single" to your boot prompts (lilo or grub) and go from there.

Quote:

Originally posted by acid_kewpie
personally i'd say kill that service... it's just a crippled version of bind which might speed u pyour dns hits by .25 seconds sometimes... as for the problem... maybe a lockfile or somethign like that, but also it might be a netowrknig thing. have you tried leaving it to timeout for a length of time? either way i'd suggest just cutting it out for now, by deleting /etc/rc5.d/S80dnscache or whatever it's going to be called on suse. this is only a symlink to the real service, so totally replacable at any point you want to. (and rc5.d is assuming you boot to X, if you use a console login, change the 5 to a 3.) if you're having a hard time getting in at all, try booting to single user mode, add a "1" or "single" to your boot prompts (lilo or grub) and go from there.

Well, I'm glad you're telling me that the service is pretty much worthless, but everthing else is greek :( I didn't make a bootdisk or anything so I don't even know where to start to kill the service. Thanks for the help!
Billy

EDIT: Oh yeah, I did give it plenty of time to timeout.

ok. at lilo or boot prompt hit e (grub) or... ctrl-x maybe in lilo (???) and add "1" or "single" to the options, and then boot. this will log you in as root and not load any services at all.

then use "rm /etc/rc5.d/<linktocacheservicewithhopefullyobviousname>" to remove it from boot. i'm not familiar with suse's /etc/ structure, might be /etc/rc.d/rc5.d, might be /etc/init.d/rc5.d.. just poke around using "ls" once deleted, reboot.

as a disclaimer, i tend to describe things in as low level way as possible, as it's more generic across platfom. maybe (like redhat / fedora) you can press "I" during a normal boot to confirm ecah service as they load? that's much nicer way if possible....