[X-Unix] debugging /etc/syslogd.conf under Leopard

William H. Magill magill at mcgillsociety.org
Sat Sep 20 12:02:37 PDT 2008


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?




T.T.F.N.
William H. Magill
# Beige G3 [Rev A motherboard - 300 MHz 768 Meg] OS X 10.2.8
# Flat-panel iMac (2.1) [800MHz - Super Drive - 768 Meg] OS X 10.4.11
# iMac6,1 Core 2 Duo [2.16GHz - 3 GB 667] OS X 10.5.5
# Mac mini Core Duo [1.66 Ghz - 2 GB 667]OS X 10.5.5
# PWS433a [Alpha 21164 Rev 7.2 (EV56)- 64 Meg] Tru64 5.1a
# XP1000  [Alpha 21264-3 (EV6) - 256 meg] FreeBSD 5.3
# XP1000  [Alpha 21264-A (EV 6.7) - 384 meg] FreeBSD 5.3
magill at mcgillsociety.org
magill at mac.com
whmagill at gmail.com






More information about the X-Unix mailing list