The problem was that the syslog daemon was up with -t parameter and MON writes to syslog through network and NOT locally.
Thanks for your answer that lead me to fix the problem. Christos Charalampous -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Roderick Schertler Sent: Wednesday, September 04, 2002 4:09 PM To: Christos Charalampous Cc: Mon Subject: [Mon] Re: About logging On Thu, 29 Aug 2002 10:59:38 +0300, "Christos Charalampous" <[EMAIL PROTECTED]> said: > > I am using mon in a Solaris 2.8 box. Mon uses /dev/console for logging > even if the syslog is running with specific entry: The most likely cause is that your syslogd doesn't listen for UDP packets. Try this test program: #!/usr/bin/perl -w use strict; use Sys::Syslog qw(:DEFAULT setlogsock); if ($^O eq 'linux' || $^O eq 'openbsd') { setlogsock 'unix' or die "can't setlogsock: $!\n";; } openlog 'syslog-test', 'cons,pid', 'daemon' or die "can't talk to syslogd: $!\n"; syslog 'info', 'hi mom' or die "error writing to syslogd: $!\n"; If you get "hi mom" on the console instead of in /var/log/daemon.info try adding your OS to the setlogsock test. If this is the case you can either patch mon the same way, or tell your syslogd to listen for UDP packets. -- Roderick Schertler [EMAIL PROTECTED] _______________________________________________ Mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon _______________________________________________ Mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
