Re: BUG #2088: logfiles only readable by instance owner

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Dick Snippe <Dick(dot)Snippe(at)tech(dot)omroep(dot)nl>
Cc: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2088: logfiles only readable by instance owner
Date: 2005-12-03 20:32:41
Message-ID: 20051203203241.GA23035@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Dec 02, 2005 at 23:30:21 +0100,
Dick Snippe <Dick(dot)Snippe(at)tech(dot)omroep(dot)nl> wrote:
>
> Using a log rotation program is possible (apache rotatelogs comes to mind),
> but that would require starting postgresql with something like
> postmaster | rotatelogs
> and just hope that rotetelogs doesn't die in the weeks or months that
> postmaster runs. Also postmaster can't be started as a daemon in this case.

You can use multilog in DJB's daemontools package to do this.

It writes the logfiles publicly readable, so you control access to them via
the directory they are contained in.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2005-12-03 21:23:07 Re: BUG #2089: Documentation bug: Triggers in plpythonu
Previous Message Dirk Pirschel 2005-12-03 20:06:28 Re: BUG #2092: No answer to bug reports 1975 and 2055