On Mon, 16 Nov 2009 17:55:51 +0200, Eray Aslan wrote: > On 16.11.2009 14:46, Neil Bothwick wrote: > > On Mon, 16 Nov 2009 09:05:18 +0200, Eray Aslan wrote: > > > >> - No need to logrotate with time based filenames. Hence, no > >> need to "kill -HUP" the syslog daemon. No missed logs. > > > > Then how do you get the server to use the new logfile names each > > day/week? > > It creates and uses a new file each hour/day/etc. Perhaps, you missed > the file(...) directive?
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. > > You only need to send a SIGHUP to the server using that log > > facility, so syslog would not be affected in your example. > > I can't parse this. The point is avoiding SIGHUP so that we do not miss > any log messages. You wouldn't miss a log messsage by sending a SIGHUP to your mail server, the logger woulsd keep running. > OP asked how one manages log files without logrotate and the answer is > with time based file names. It has the additional benefit of avoiding > SIGHUP. I understood both the question and answer, but it seems like you are avoiding logrotate by re-implementing it in your scripts. -- Neil Bothwick An example of hard water is ice.
signature.asc
Description: PGP signature
