Change 'pg_ctl: no server running' Exit Status to 3

From: "Aaron W(dot) Swenson" <aaron(dot)w(dot)swenson(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Change 'pg_ctl: no server running' Exit Status to 3
Date: 2011-05-24 00:50:53
Message-ID: 4DDB00ED.8040301@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----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.

Sincerely,
Mr. Aaron W. Swenson

[1]
http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREIAAYFAk3bAO0ACgkQCOhwUhu5AElmsQEAs5rqihVYnglG1l8tiAVE7LZ+
vGq8+YFxRrqlPEt0kQIA/0PIdnf9xlnNewPCZuMRk/uOOeMHBptcDMSTuaWI3QBU
=td0Z
-----END PGP SIGNATURE-----

Attachment Content-Type Size
pg_ctl-exit-status.patch text/plain 414 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-05-24 01:15:27 Re: Reducing overhead of frequent table locks
Previous Message Kevin Grittner 2011-05-23 23:50:01 Re: SSI predicate locking on heap -- tuple or row?