Re: starting server at boot

From: "Adam Lang" <aalang(at)rutgersinsurance(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "PGSQL General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: starting server at boot
Date: 2000-09-05 19:38:12
Message-ID: 028b01c01770$d3ffb320$330a0a0a@Adam
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

No, still no luck. I'm putting the line in at the end of the rc.local file.
I know it gets to it because, when the nohup is in front, it generates a
message.

But I am not able to connect to the dataabse after reboot.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Adam Lang" <aalang(at)rutgersinsurance(dot)com>
Cc: "PGSQL General" <pgsql-general(at)postgresql(dot)org>
Sent: Friday, September 01, 2000 5:45 PM
Subject: Re: [GENERAL] starting server at boot

> "Adam Lang" <aalang(at)rutgersinsurance(dot)com> writes:
> > nohup su -c 'postmaster -i -D /usr/local/pgsql/data > server.log 2>&1'
> > postgres &
>
> nohup su seems a little odd; I'd expect the nohup command to affect the
> su process itself, but I'm not at all sure that su would allow the
> nonstandard signal-handling state to propagate through to the command
> it executes.
>
> Try
> su -c 'nohup postmaster ... 2>&1 &' postgres
> instead.
>
> This should also eliminate nohup's desire to make a useless output
> file...
>
> regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adam Lang 2000-09-05 19:39:13 Re: install 7.0.2 host
Previous Message Zeljko Trogrlic 2000-09-05 19:00:46 Re: Report of performance on Alpha vs. Intel