On Vie 15 Jun 2001 21:08, you wrote:
> >>>>> "LO" == Lamar Owen <lamar.owen@wgcr.org> writes:
>
> LO> Then whose fault is that? Is it our syslog calling, or the
> LO> receiving syslog not hearing? (Yes, I know that by default syslog
> LO> uses UDP)....
>
> Not on FreeBSD (probably most other BSD's as well), the default is to
> use a named pipe.
>
> Anyhow what is the best way to make postgres stop stderr logging when
> syslog logging is turned on? Right now I use "-l /dev/null" to pg_ctl
> when starting the server. This seems to me that the server will still
> waste cycles doing the stderr printing.
Talking aout sql.log rotate, my rotates are quite strange, or give strange
results. After a rotate I have an sql file that has a binary part at the
begining, and after quite a few pages of ^@s the logs, properly, starts.
I'm using this script to rotate syslog, maillog, etc. but I'm having trble
with sql.log.
Saludos.... ;-)
It's rotating, but the file that is left to have he output of postgres has a
bunch of bianry data first, and then the log.
--
Cualquiera administra un NT.
Ese es el problema, que cualquiera administre.
-----------------------------------------------------------------
Martin Marques | mmarques@unl.edu.ar
Programador, Administrador | Centro de Telematica
Universidad Nacional
del Litoral
-----------------------------------------------------------------
