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.