hi joel,
just checked -- looks ok. PID is properly 'owned & operated' by the
postmaster superuser defined in the launch command
Who owns /var/run? What group? Does testuser have permission to delete
files there? (May need to add testuser to the wheel or admin group?)
good points =) already done,
(From someone else who doesn't know what doesn't know, ... :-/)
>sudo -u testuser sh -c "nohup /usr/local/pgsql/bin/postmaster [...]
...
> >> note that my cmd line refers to the conf file, which has the external
> >> PID id'd in it:
> >
> >> external_pid_file = '/
hi,
But who is it owned by, and with what permissions?
same owner as postmaster, 0644 or 0600
If you do the "touch" as some other user than the postmaster runs as, it's
very
plausible the postmaster can't write the file. (That doesn't yet
explain why it goes south afterward, but first we need to
OpenMacNews <[EMAIL PROTECTED]> writes:
> stop postgres
> touch PIDfile (if _not_ there)
> reboot
> --> NO launch, nothing in the logs
> verify PIDfile exists ... it does
But who is it owned by, and with what permissions? If you do the
"touch" as some other user than the postm
hi,
note that my cmd line refers to the conf file, which has the external
PID id'd in it:
external_pid_file = '/var/run/postgresql.pid'
Oh, now you tell us ;-)
heh. sorry -- just thought it was SOP.
in case you haven't noticed, i'm at that 'wunnerful' ramp-up stage that i dunno
what i dunn
OpenMacNews <[EMAIL PROTECTED]> writes:
> note that my cmd line refers to the conf file, which has the external
> PID id'd in it:
> external_pid_file = '/var/run/postgresql.pid'
Oh, now you tell us ;-)
Still, I'm not sure what could be the problem. The only code that
reacts to that setting
hi tom,
In that case it's a problem in your launch script. The postmaster
doesn't even know that such a file exists; it keeps its lock file
in the data directory.
well, h.
the launch script is currently simplified (for testing) to just the
pid-checking-if-stmt + the single line launch cmd. t
OpenMacNews <[EMAIL PROTECTED]> writes:
> although i've seen nothing pid-related in my logs, preceding my startup file
> launch cmd with a pid check/delete:
>if [ -f /var/run/postgresql.pid ]; then
>rm -rf /var/run/postgresql.pid
>fi
>(launch cmd)
> seems to have done the tri
hi tom,
LOG: 0: logger shutting down
LOCATION: SysLoggerMain, syslogger.c:361
I should have twigged to that before --- if you're running the syslogger,
then nothing except very early startup messages is going to go to
stderr. Look in wherever you told it to put the log output.
i thou
