an effective way to restart syslogd

| 1 Comment | No TrackBacks

I've been busy modifying the syslogd.conf file on various servers to additionally send entries to a central syslog server. Getting syslogd to restart properly after modifying the conf file proved to be more problematic than it should be.

You'd think you'd be able to use a kill -HUP, but that's not appropriate here. You'd think you'd be able to issue a launchctl stop command, but that doesn't do it either. If you just kill it, even with a -9 flag, you'll see launchd just happily pops up a new one. That was my case, but the new syslogd wasn't actually logging.

Instead, what worked for me was to issue this command.

root# launchctl unload /System/Library/LaunchDaemons/; sleep 1; launchctl load /System/Library/LaunchDaemons/  

No TrackBacks

TrackBack URL:

1 Comment

My syslogd started using >99% proc and this worked for restarting it.

Leave a comment

About this Entry

This page contains a single entry by Noah Abrahamson published on March 4, 2008 6:24 PM.

Compiling WebAuth for Leopard's Apache2 was the previous entry in this blog.

Autoset SSH GSSAPIDelegateCredentials on MacOS X is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.