Anyone know how to restart Rendezvous without restarting the entire machine? I've tried the following:
Rendezvous doesn't show up as a process in Process Viewer (this is on a Jaguar machine) or Top
log into console, sudo kill inetd
log into console, sudo kill nfsiod
I did find out that those processes can be killed without bringing down OS X (whew)! I just can't figure out where Rendezvous hides. But I've verified with Rendezvous Browser that Rendezvous died at some point.
I know I can restart the machine and it will be OK. But I'm trying to not have to restart it. Everything else is running great.
voldenuit
05-28-2005, 06:39 AM
Killing random deamons will generally kill, not relaunch them.
Look through he /etc/rc file to find out what is launched on boot, I don't remember how rendezvous was called in Jaguar, I think it was mdns.
I'd also relaunch inetd the way it is in rc.
styrafome
05-28-2005, 11:05 AM
I think I just don't know the right command. I only know the kill command and then to call the name of the process to launch it again if it doesn't come back up on its own. What's the command to relaunch a process in one step?
darelon
05-28-2005, 05:45 PM
I have never worked with Jaguar, but in Panther and Tiger the /usr/sbin/mDNSResponder daemon is responsible for ZeroConf/Rendezvous/Bonjour functionality.
You can have it dump a somewhat cryptic status summary to the system log withsudo killall -INFO mDNSResponder
And if necessary, you should be able to restart it withsudo killall -HUP mDNSResponder
See also the mDNSResponder(8) and mDNS(1) manual pages.
voldenuit
05-28-2005, 06:07 PM
While the HUP signal is technically correct, I only use it to have working daemons re-read their config-files.
Misbehaving daemons get killed, if need be even with kill -9, then relaunched.
Daemons should be robust enough not to hang, if they do anyway, I don't trust them any longer.
styrafome
05-29-2005, 12:20 AM
Well, that suggestion to try restarting mDNSResponder seemed to fix it, if anyone else ever needs to do this. It's kind of hard to tell because I was also playing around with firewall settings, which never fixed it before, and ultimately, it all sort of popped up working after I decided to sleep and wake the machine. I guess it needed to leave and re-enter the network for one of those changes to "take." (Note: Sleeping and waking never fixed it before so it was definitely due to something I fiddled with.)
Thanks for all the advice, this "UNIX Newcomer" learned something today.
TOP
