Thread

1. PgLOGd

   Thomas T. Thai <tom@minnesota.com> — 2003-04-09T04:22:15Z

   I stumbled on PgLOGd and what I read was wonderful. If you use it, I'd
   like to hear of your comments. Unfortunately the last update was
   over a year ago. Anyone know if Matthew Hagerty is still working on it?
   
   The nice thing about it is that it works regardless of Apache API changes.
   And no additional spawning of child process as with using pipe with
   logging tools.
   
   And ofcourse it requires Postgresql.
   
   --
   Thomas T. Thai
   
   
   

2. Re: PgLOGd

   Mike Benoit <mikeb@netnation.com> — 2003-04-09T16:35:08Z

   I installed it a few weeks ago on a test box and was quite impressed. It
   has some very nice features to handle cases when the database can't
   handle the load or if it goes down completely. I haven't used it in a
   production enviroment yet, but I would like to. 
   
   On Tue, 2003-04-08 at 21:22, Thomas T. Thai wrote:
   > I stumbled on PgLOGd and what I read was wonderful. If you use it, I'd
   > like to hear of your comments. Unfortunately the last update was
   > over a year ago. Anyone know if Matthew Hagerty is still working on it?
   > 
   > The nice thing about it is that it works regardless of Apache API changes.
   > And no additional spawning of child process as with using pipe with
   > logging tools.
   > 
   > And ofcourse it requires Postgresql.
   > 
   > --
   > Thomas T. Thai
   > 
   > 
   > ---------------------------(end of broadcast)---------------------------
   > TIP 4: Don't 'kill -9' the postmaster
   -- 
   Best Regards,
    
   Mike Benoit
   NetNation Communications Inc.
   Systems Engineer
   Tel: 604-684-6892 or 888-983-6600
    ---------------------------------------
    
    Disclaimer: Opinions expressed here are my own and not 
    necessarily those of my employer
   
   
   

3. Re: PgLOGd

   Thomas T. Thai <tom@minnesota.com> — 2003-04-09T16:55:36Z

   > I installed it a few weeks ago on a test box and was quite impressed. It
   > has some very nice features to handle cases when the database can't
   > handle the load or if it goes down completely. I haven't used it in a
   > production enviroment yet, but I would like to.
   
   After testing it, I put it on a production server. Been running since last
   night without any problems. With an insert on each web page load, it does
   kick up the server load on the Postgresql server.
   
   PgLOGd is a very effective solution for a server farm. No need to worry
   about rotating logs and gluing them all together.
   
   Thomas