On Tue, 17 Nov 2009 14:08:00 +0200, Eray Aslan wrote: > > I didn't miss it. My question was how to you get the process to USE > > the new file. Unless you SIGHUP the process, it will continue using > > the config in pace when it started. > > Last sentence is correct. What you are missing is that the config says > to start a new file each day/hour/etc. syslog-ng does not evaluate the > file() expression once at startup and then treat it as a constant.
Ah, it makes sense now. > > You wouldn't miss a log messsage by sending a SIGHUP to your mail > > server, the logger would keep running. > > When syslog-ng cannot process messages for whatever reason, it will > buffer them. When the buffer is full, it will drop the messages. There > is no need to add to the load and increase message loss probability with > SIGHUP (think of a central log server). How does sending a SIGHUP to smtpd increase the load on the syslog server? -- Neil Bothwick Warp 5.. engage. No, no, Mr. Data, more clutch!
signature.asc
Description: PGP signature
