I agree with Adrian. If this is on a Linux system, I'd suggest setting up "icrond" to monitor that file and at least record who is accessing it. In addition, I would suggest that said Linux system run with SELinux in "enforcing" mode. That can stop even "root" from updating something, if it doesn't have the proper SELinux credentials.
On Mon, Nov 16, 2015 at 11:06 PM, Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:
On 11/16/2015 06:59 PM, M Tarkeshwar Rao wrote:
Hi All,
In our production setup we found new issue as postgreSQL.conf has become
zero byte file.
After some time we copied that file from some back up, after some time
it has again become zero byte.
Any clue what is the reason of this behavior.
I tend to doubt that Postgres is zeroing out its own conf file. My guess is some other program/script is doing that. If you can narrow down the time frame this happening, I would then look for any cron/scheduled jobs that are running at the same time.
Regards
Tarkeshwar
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Schrodinger's backup: The condition of any backup is unknown until a restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
