To check for problems in your syslog.conf file, find the command that's run from /etc/init.d/syslog and run the same command with the -d option from a terminal/ssh window that allows you to scroll back thru the history. This debug option will display copious information as it processes the conf file, including any errors it finds. In debug mode, syslogd doesn't go into daemon mode, so you need to kill it with a ^C after you get the info you need. Make the necessary changes to syslog.conf, then '/etc/init.d/syslog start'.
Bob At 08:49 AM 10/16/02 -0700, David Meissner wrote: >Open /etc/syslog.conf with vi, then type ":set list" (without the quote >marks). This will show non-printing characters and will show you if there >are any spaces between the fields in the file. There should only be tabs >between the entries, no spaces. On my screen the tabs are represented by the >combination ^I. > >If the file is correct, and you have stopped/started syslogd (full stop, not >just a HUP), and the logger command still doesn't work, then something is >seriously wrong with your syslogd. > >David Meissner > > > >-----Original Message----- >From: Oliver Schlag [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, October 16, 2002 8:10 AM >To: [EMAIL PROTECTED] >Subject: Re: newbie > > >Hy, > >another possible thing is that you have used whitespaces in your syslog.conf >file to separate keys from values. I think I remember syslog doesn't really >loves this. Check your syslog.conf file for this and then restart your >syslog with /etc/init.d/syslog stop and then /etc/init.d/syslog start. > >Mit freundlichen Gr��en > >Oliver Schlag >Technik / Anwendungsentwicklung >Blue Onlineservices
