[MacPorts] #24958: postgresql84-server.wrapper forces logfile into an unwritable directory
MacPorts
noreply at macports.org
Thu May 20 07:30:24 PDT 2010
#24958: postgresql84-server.wrapper forces logfile into an unwritable directory
-------------------------------------------+--------------------------------
Reporter: ashley.moran@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.8.2
Keywords: | Port: postgresql84-server
-------------------------------------------+--------------------------------
Yesterday I was trying to tune the logging of my local Postgres
installation and I was having trouble finding the file. I found a log
file in /opt/local/var/log/postgresql84 but I wanted to have it date-
rotated. After changing the config, I was still confused where it was
logging, so I deleted postgres.log. Then Postgres wouldn't start up
again.
Eventually I figured out that
/opt/local/etc/LaunchDaemons/org.macports.postgresql84-server/postgresql84-server.wrapper
overrides the log file with "-l
/opt/local/var/log/postgresql84/postgres.log". BUT, this is a directory
that the postgres server can't write to.
I lost an hour figuring out what was going on, even resorting to rebooting
the machine.
I can see the appeal of having the log in a directory you can read as a
non-postgres user. But, forcing Postgres to log to a directory it can't
write to prevents you from doing the perfectly ordinary maintenance task
of deleting log files.
I'd like to see this improved. Possibilities include making a subfolder
of /opt/local/var/log with more usable permissions, or just not using the
-l flag at all.
--
Ticket URL: <http://trac.macports.org/ticket/24958>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list