Re: logging problem ... ?

D'oh ... there ya go, lotsa days flying through now ...

On Mon, 8 May 2000, Tom Lane wrote:

> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> > cat ~pgsql/pgstart ... postmaster's own debug output? ya know, for some
> > stupid reason, the only thing i'm capturing is postgres's output :( I
> > just modified the pgstart script and restarted the server, so postmaster's
> > output is to logs/postmaster.5432 ...
>
> Oh, I see the problem! It's the -S in the postmaster switches:
>
> ${POSTMASTER} -d 1 -B 4096 -N 128 -S \
> ^^
>
> That redirects postmaster's stdout/stderr to /dev/null, so you never
> see anything in its log except for a message or two that comes out
> before -S is processed. Instead of -S you should be using
>
> nohup ${POSTMASTER} same-switches-except-S \
> </dev/null >& logs/postmaster.${PORT} &
>
> (I'm not sure if redirecting stdin to /dev/null is really necessary on
> your OS, but it is on mine.)
>
> regards, tom lane
>

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org