On Sep 20, 2008, at 2:02 PM, William H. Magill wrote: > In the "good old days," (of Unix and OS X) one could simply kill off > syslogd, and restart it as "syslogd -d". > It would hang around nicely on your terminal and tell you what was > wrong with your conf file. > > That technique no longer works. Nor does adding the -d flag to > the .plist file. > > It (launchd) apparently runs syslogd with the -d flag, but no output > appears anywhere that I can find. > > Without launchd, syslogd generates an error if you try to run "/usr/ > sbin/syslogd -d" directly from the terminal. > > So the basic question is ... does syslogd still provide the "syntax/ > error checking which the man page claims it does? 1) man launchd 2) man launchctl HTH --- Eric Crist