On Wed, Jul 16, 2003 at 12:40:06PM +0200, Guillaume Fougnies wrote: > Wed, Jul 16, 2003 at 11:07:47AM +0100: Jez Hancock wrote: > > I would do this but we wanted to give our users 'live' logfiles, rather > > than making them wait until log rotation before being able to view them > > (or did I misunderstand you?). > > During my work on the ENodes project, i've developed a tiny threaded logger > in c to manage internal logfiles (by webmaster/website/version). > (you can rewrite it in perl with a 5.8.x built with thread...) > > Perl handlers send log lines through a UNIX socket to the logger which > is opening logfiles when needed and keeping them opened. > It avoids the overhead of opening and locking each time the file and > provides as many online debug logfile as you ask. /me nods. This would save a lot of overhead. The only benefit of opening a new pipe each time I suppose is that you don't need to worry about rotation.
> The logger is launched in a 'PerlRequire' file. > The client have a persistant connection to the logger. > > If it fits your needs, you can get sources here: http://www.enodes.org > Server : utils/enodes_logger/enodes_logger.c > Client module : enodes_core/modules/ENodes/Core/ApLog.pm Many thanks, I'll investigate now. Well ENodes sounds very interesting, particularly the part about webmasters being able to test new versioning without applying changes and the reduced httpd restart feature. Very interesting. Will certainly have a look at this, we're currently considering something called webcp, a PHP project which has much potential but is sitll unfortunately very much in beta. Thanks! -- Jez http://www.munk.nu/
