Re: Definitive logrotate solution?
От | Wells Oliver |
---|---|
Тема | Re: Definitive logrotate solution? |
Дата | |
Msg-id | CAOC+FBVC7xxsTWPEdy0zpDMzhvi+i-mzdw616MG+6uWhxv_YGQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Definitive logrotate solution? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Definitive logrotate solution?
|
Список | pgsql-admin |
How do you ensure you're not keeping logs from 35+ days ago, or whatever? Just a find -mtime +10 -exec rm {}\; kind of thing?
--
Wells Oliver
wellsoliver@gmail.com
On Wed, Apr 11, 2012 at 4:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Wells Oliver <wellsoliver@gmail.com> writes:Use the logging collector with its built-in rotation parameters, and you
> Might anyone share theirs? My log_rotation is set to 'stderr', and the log
> files are being put into /var/log/postgresql.
> My main concern is the postrotate action-- want to make sure the log is
> properly rotated, unneeded older logs removed, and postgres... properly
> bounced?
don't need anything else.
If you insist on an external solution, there's basically no way except
to shut down and restart postgres after any rotation, because there are
going to be N processes all connected to the same stderr file descriptor.
regards, tom lane
Wells Oliver
wellsoliver@gmail.com
В списке pgsql-admin по дате отправления: