From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | "Aaron W(dot) Swenson" <aaron(dot)w(dot)swenson(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Change 'pg_ctl: no server running' Exit Status to 3 |
Date: | 2011-06-03 16:11:30 |
Message-ID: | BANLkTikPzQKDcg1ui4Pmi9ErQxD_czePpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 23, 2011 at 8:50 PM, Aaron W. Swenson
<aaron(dot)w(dot)swenson(at)gmail(dot)com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> According to Linux Standard Base Core Specification 3.1 [1], the exit
> status should be '3' when the server isn't running.
>
> I've attached a very simple patch that resolves this cosmetic issue,
> which applies to all branches.
>
> My initial search regarding other platforms has turned up nil. It looks
> like they just check for a zero or non-zero exit status.
>
> As for the necessity of the patch: Gentoo Linux uses pg_ctl in all of
> its initscript actions for PostgreSQL. I'd imagine that Gentoo is not
> the only distribution that takes advantage of pg_ctl for its initscript
> actions.
I'd be disinclined to back-patch this as it might break things for
people. But I see no harm in applying it to master, if nobody
objects...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-06-03 16:12:19 | Re: Identifying no-op length coercions |
Previous Message | Radosław Smogura | 2011-06-03 16:09:48 | Re: BLOB support |