bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: feeping creaturism


From: James Morrison
Subject: Re: feeping creaturism
Date: Mon, 11 Mar 2002 10:56:19 -0800 (PST)

--- Oystein Viggen <oysteivi@tihlde.org> wrote:
> * [Adam Olsen] 
> 
> > Just one question.  Does apache keep the log open long term, or
> does
> > it open and close it for each item it writes?  If it keeps it
> open
> > you'll have the problem that the log never rotates (it'd keep the
> old
> > file open), unless you split out individual lines, but then you'd
> need
> > special handling to keep apache's pairs of lines together.
> 
> In Debian's /etc/cron.daily/apache that currently does log
> rotating,
> the program is sent a SIGHUP to reopen its log file.  The easiest
> way of
> getting the filemuxing to work would probably be to use cron to HUP
> the
> server (but that kind of defeats the point of the whole translator
> setup).
> 

 Having a cron job HUP apache whenever I need is isn't completely
against the point, but is not the ideal solution.  The advantage of
only having cron HUP apache is that if the machine goes down, the
logs still rotate anyway.  My other option is to write a patch for
apache that creates an option to open the file each time the file is
written to, or some optimized version of this.

It seems gopherd, smbd, and nmbd all would need a SIGHUP as well.

At least I can feel comfortable that this will work for my changelogs
when I am working this summer ;)  It will also work as my ogg
playlist, but that will require an nfsd on my machine as well.  So
many fun things to do, so little time.


=====
James Morrison
   University of Waterloo
   Computer Science - Digital Hardware
   2A co-op
http://hurd.dyndns.org

Anyone refering this as 'Open Source' shall be eaten by a GNU

__________________________________________________
Do You Yahoo!?
Try FREE Yahoo! Mail - the world's greatest free email!
http://mail.yahoo.com/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]