Skip site navigation (1) Skip section navigation (2)

Re: Linux start script updates

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Linux start script updates
Date: 2010-03-01 16:56:45
Message-ID: 4B8B9D6D020000250002F740@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
 
> I think though that the answer to Peter's question is that "stop"
> has to be special cased to some extent, because it is not supposed
> to be an error to stop a service that's not running.  If it's not
> even installed, then a fortiori it's not running, so the exit code
> *must* be 0 not 5 in that case.
 
Exactly.  With Fedora respecting the standard in this regard, I'm
convinced we should, too.  In reviewing things based on Peter's
question, I did start to have doubts about *not* special-casing
"status" -- it has its own set of values and 5 is not assigned, so
using it seems wrong.  It seems like it should be 3 ("program is not
running").  Agreed?
 
-Kevin

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-03-01 17:04:38
Subject: Re: Linux start script updates
Previous:From: Andrew DunstanDate: 2010-03-01 16:52:50
Subject: Re: Re: pgsql: add EPERM to the list of return codes to expect from opening

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group