Re: [7.0.2] rotating log files ... - Mailing list pgsql-admin

From Mitch Vincent
Subject Re: [7.0.2] rotating log files ...
Date
Msg-id 00c501c0111d$7e1dcd60$0200000a@doot
Whole thread Raw
In response to [7.0.2] rotating log files ...  (The Hermit Hacker <scrappy@hub.org>)
Responses Re: [7.0.2] rotating log files ...
Re: [7.0.2] rotating log files ...
List pgsql-admin
Can you move the logfile then touch the original file to create an empty
one?

*shrug* just an idea :-)

-Mitch

----- Original Message -----
From: "The Hermit Hacker" <scrappy@hub.org>
To: <pgsql-admin@postgresql.org>
Sent: Monday, August 28, 2000 10:59 AM
Subject: [ADMIN] [7.0.2] rotating log files ...


>
> can someone recommend on how to rotate the following log files without
> having to stop/start the server?
>
> postgres 85333 pgsql    1w  VREG  13,131084       995 762037
/pgsql/logs/postmaster.5432.61308
> postgres 85333 pgsql    2w  VREG  13,131084 316501241 762038
/pgsql/logs/5432.61308
>
> its the 316meg one and growing that I'm more interested in doing,
obviously ...
>
> I'm starting my postmaster as:
>
> #!/bin/tcsh
> setenv PORT 5432
> setenv POSTMASTER /pgsql/bin/postmaster
> unlimit
> ${POSTMASTER} -B 384 -N 192 \
>               -o "-F -o /pgsql/logs/${PORT}.$$ -S 32768" \
>               -i -p ${PORT} -D/pgsql/data >&
/pgsql/logs/postmaster.${PORT}.$$ &
>
> where I was hoping that the '-o /pgsql/logs/${PORT}.$$' would create a
> 'per postgres process' log file, but $$ is taking on the PID of the parent
> process, not the children ...
>
> suggestions?
>
> Marc G. Fournier                   ICQ#7615664               IRC Nick:
Scrappy
> Systems Administrator @ hub.org
> primary: scrappy@hub.org           secondary:
scrappy@{freebsd|postgresql}.org
>
>


pgsql-admin by date:

Previous
From: The Hermit Hacker
Date:
Subject: [7.0.2] rotating log files ...
Next
From: Lamar Owen
Date:
Subject: Re: [7.0.2] rotating log files ...