From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Massimo Dal Zotto <dz(at)cs(dot)unitn(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Syslog and pg_options (for RPMs) |
Date: | 2001-02-08 20:56:02 |
Message-ID: | 12928.981665762@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> AOLserver is one example that successfully redirects dynamic linker
> messages to it's own log.
Oh? How? Are you sure they're not just piping stderr to a program
of their own devising? That's basically what I'm recommending.
> Is syslog not portable enough?
It's got a lot of limitations and problems of its own, on many
platforms... but the fundamental point is that without an external
redirector, we are never going to get everything of interest sent
to syslog.
> A syslogger of stderr would make a nice place to pipe the output :-).
> 'postmaster .... 2>&1 | output-to-syslog-program -f facility.desired' or
> some such. But that obviates the need to support syslog _at_all_ in the
> backend,
Precisely my point. I think working hard on syslog support inside elog
is misplaced effort.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2001-02-08 21:00:12 | Re: Syslog and pg_options (for RPMs) |
Previous Message | Dominic J. Eidson | 2001-02-08 20:52:14 | Re: Syslog and pg_options (for RPMs) |