Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'If lookupd is the problem...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
If lookupd is the problem...
Authored by: gfoyle on Oct 17, '05 09:32:43AM
If lookupd is the problem, have you tried just restarting it? You could use something like
kill -9 `cat /var/run/lookupd.pid`; /usr/sbin/lookupd
(I have not tested this command so I am not sure if this is the exact syntax.)

[ Reply to This | # ]
If lookupd is the problem...
Authored by: sjk on Oct 17, '05 02:36:30PM

-9 (SIGKILL) is overkill (pun intended?) and should only be tried when a process can't be killed with some other signal. What you probably want here is:

sudo killall lookupd

or:

sudo killall -HUP lookupd



[ Reply to This | # ]
If lookupd is the problem...
Authored by: TigerKR on Oct 17, '05 07:05:40PM

Restarting lookupd is exactly what unlockupd is supposed to do. But It doesn't appear to work all of the time. And when unlockupd doesn't work, you can't log-in to a headless server to restart lookupd.



[ Reply to This | # ]