It's not normally a good idea to move/remove files that a process has an
open file handle for. The safest way is to copy the file to a new
location/name then cat /dev/null > logfile
Chris
Mitch Vincent wrote:
>
> 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
> >
> >