Sorry, should point out that the stop is resulting from executing a ^c after
running the script manually. Since the script runs... postgres starts, but
from reading the startup script, it is waiting for the pid file to appear before
reporting suscess... and it isn't doing this. Or at least not exiting and
leaving the postmaster running. It just sits there... thus the ^c to regain the
terminal.
opening two terminals, I can run the start script, and while the first terminal
is sitting there waiting for the script to release control, move to the second
terminal and view the results... postmaster running fine, pid file there, all
normal.
if I execute the script with the & behind it, it allows everything through after
entering another <cr> which from what I can see suspends the session which then
clears normally. (making sense?)
Confused still as to the cause or how to rectify.
Dave
>-----Original Message-----
>From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
>Sent: Sunday, March 10, 2002 11:22 AM
>To: Dave
>Cc: pgsql-admin@postgresql.org
>Subject: Re: [ADMIN] Postgres not starting at boot(FreeBSD) - startup
>script not releasing
>
>
>"Dave" <dave@hawk-systems.com> writes:
>> DEBUG: Data Base System is starting up at Sat Mar 9 17:05:45 2002
>> DEBUG: Data Base System was shut down at Sat Mar 9 17:05:39 2002
>> DEBUG: Data Base System is in production state at Sat Mar 9 17:05:45 2002
>> Fast Shutdown request at Sat Mar 9 17:05:48 2002
>> DEBUG: Data Base System shutting down at Sat Mar 9 17:05:48 2002
>> DEBUG: Data Base System shut down at Sat Mar 9 17:05:48 2002
>
>It looks like something is hitting the postmaster with a SIGINT signal
>as soon as it starts. Got any idea what might be doing that? It's
>not pg_ctl, for sure (unless the "something" is firing your init
>script with a 'stop' option). In any case I think you should be looking
>for outside agencies, not a problem directly in this init script.
>
> regards, tom lane
>