Re: Linux LSB init script - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Linux LSB init script
Date
Msg-id 603c8f070909201954j718d2b6ep5343d1a1605cf168@mail.gmail.com
Whole thread Raw
In response to Re: Linux LSB init script  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Linux LSB init script
List pgsql-hackers
On Thu, Sep 17, 2009 at 4:52 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Sep 17, 2009 at 4:18 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> On tor, 2009-09-17 at 11:59 -0500, Kevin Grittner wrote:
>>> > Well, in such cases it may be useful to add an option such as
>>> > --oknodo to select the idempotent behavior.
>>>
>>> I found that confusing (as did Robert); how about --lsm-conforming?
>>
>> s/lsm/lsb/
>>
>> I'm not so sure that I would label it as LSB, because that is too broad,
>> and not very descriptive.
>>
>> I think this option should only control whether start and stop are
>> idempotent.  Other LSB issues such as exit codes ought to become the
>> default, or possibly a different option if necessary.
>
> Maybe we should just call it --idempotent.
>
> Or, they could be additional actions, like ensure-start/ensure-stop.

It seems like there is some support for what this patch is trying to
do, but much disagreement about the details of how to get there.
Where do we go from here?

...Robert


pgsql-hackers by date:

Previous
From: Emmanuel Cecchet
Date:
Subject: Re: generic copy options
Next
From: Robert Haas
Date:
Subject: Re: TODO item: Allow more complex user/database default GUC settings