Hi Dave,
Attached is a patch that allows pgagent to immediately log messages to file.
I have tentatively changed the cmd line switch for logging verbosity to "-s"
so "-l" can be used for the log file specification. I felt that this was
more intuitive.
If the patch is accepted, then a small change to the init script will need
to be made to accommodate the file logging...
Cheers
Jeremy
> -----Original Message-----
> From: Dave Page [mailto:dpage@vale-housing.co.uk]
> Sent: Tuesday, 13 June 2006 1:35 a.m.
> To: Jeremy Palmer; pgadmin-support@postgresql.org
> Cc: Devrim GUNDUZ
> Subject: RE: [pgadmin-support] init script for redhat
>
>
>
> > -----Original Message-----
> > From: pgadmin-support-owner@postgresql.org
> > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of
> > Jeremy Palmer
> > Sent: 04 June 2006 13:18
> > To: pgadmin-support@postgresql.org
> > Subject: Re: [pgadmin-support] init script for redhat
> >
> > Ok I have attached a modified init script, which now uses the postgres
> > database. The logging is also redirected to pgagent.log in
> > the pgsql home
> > directory. Could this please be added to the source tree?
>
> Sure - thanks.
>
> Devrim; I was thinking of adding this to pkg/redhat, and leaving
> installation up to the RPM (ie. Not installed by 'make install' because
> it won't know what is or isn't an appropriate platform) - does that seem
> reasonable to you?
>
> > Note: because pgagent does not flush the buffer for every log
> > message, the
> > log file does not see anything until the buffer is written.
> > Maybe pgagent
> > could be changed to log to a file which is flushed
> > periodically, instead of
> > stdout?
>
> A command line option to specify a logfile to use instead of stdout
> would work, as might simply fflush()'ing stdout.
>
> Care to work up a patch? :-)
>
> Regards, Dave.
