On Thu, 26 Sep 2002, nate wrote: > > Also, I modified my client's syslog.conf with *.* <tabs> @my.log.server > > but the logs are not arriving. I restarted klogd and sysklogd, and they > > are running, but no logs are being sent to my server.
> as someone else reccomended, try the 'logger' program(neat program, > I had not heard of it before). depending on the kind of event will > depend on what file it ends up in, you may want to install the > xtail package to monitor all the logs at once. and at least on my > freebsd system I have to start syslog-ng BEFORE i start the local > syslog daemon otherwise the local syslog daemon takes over the port > and syslog-ng cannot bind to it. Do you mean you are running BOTH syslog-ng and syslogd ? I tried the logger and it worked from my server. I just removed syslog-ng and reinstalled syslogd...for some reason it wouldn't log anything anymore, although my syslog-conf looks fine I think. (http://bolderman.xs4all.nl/~dick/syslog-conf) > OH, and in the syslog-ng.conf at the top note it is configured to > bind to a specific IP address, if you did not change that to fit > your network then of course it won't work. The address I used is the one from the nic which is connected to the lan. I'm sorry this is taking so long, but it just seems to fail somewhere, and although i've read the syslog-ng manual, I can't find the problem... -- D.J. Bolderman [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
