On Fri, 17 Dec 2004 10:49:13 +0100, Thomas Hood wrote:
[...]
> The idea behind
> initscripts is that they do what they are told when they are run.
> sysv-rc and file-rc implement two different schemes for
> determining when they are run and with what arguments. I don't
> see why people keep trying
It has been suggested that you install symlinks[*] but provide an
/etc/default/foo file with an environment variable that forcibly
disables the service when set to "off" or whatever, and that the
initscript be written so that it overrides this forced disabling
when run from the command line. Of co
I wrote:
> If you also want to prevent the service from being started on a runlevel
> change you have to do something else such as checking $0.
Init exports RUNLEVEL, PREVLEVEL, and INIT_VERSION. Thus INIT_VERSION will
be set if you are booting or changing runlevels.
--
John Hasler
I wrote:
> Your script should check [$PREVLEVEL]. It will be N if you are booting.
Nicolas writes:
> That's a nice idea, but do you know how fine it would behave with things
> like file-rc?
It should work fine. Note that this method _only_ controls script
execution at boot time. If you also wa
On Fri, Dec 17, 2004 at 02:16:00AM +0100, Nicolas Boullis wrote:
> > if the package is removed, the init script should just exit with 0
> > status. removing the links during purge would also be appropriate.
>
> So you think lintian is wrong to complain?
no, i think lintian is correct to complain
Hi,
On Thu, Dec 16, 2004 at 09:13:43AM +0100, Adrian von Bidder wrote:
> On Thursday 16 December 2004 00.34, Nicolas Boullis wrote:
> [de-installing run-level links that weren't installed]
>
> How about installing links as /etc/rc?.d/K??foo - so the links are there and
> are properly manageable,
On Thu, Dec 16, 2004 at 12:53:27AM -0500, sean finney wrote:
> On Thu, Dec 16, 2004 at 12:34:21AM +0100, Nicolas Boullis wrote:
> > But a user felt concerned that, in the future, he may remove the package
> > and forget to delete the links. Then I thought I could remove the links
> > in postrm on
Hi,
On Thu, Dec 16, 2004 at 09:32:08AM +0100, Javier Fernández-Sanguino Peña wrote:
>
> Well, you could have a message saying that you need to enable foo and a
> 'force-start' action that started it regardless of what's in /etc/default.
That might be a solution. Users would certainly be less con
Hi,
On Wed, Dec 15, 2004 at 08:47:43PM -0600, John Hasler wrote:
> Your script should check $PRERUNLEVEL. It will be N if you are booting.
That's a nice idea, but do you know how fine it would behave with
things like file-rc?
Nicolas
On Thu, Dec 16, 2004 at 02:11:06AM +0100, Nicolas Boullis wrote:
> Hi,
>
> On Wed, Dec 15, 2004 at 04:33:49PM -0800, Russ Allbery wrote:
> >
> > A technique that I've used in packages with this issue is to install the
> > rc*.d symlinks by default, but also have the init script check a file in
>
On Thursday 16 December 2004 00.34, Nicolas Boullis wrote:
[de-installing run-level links that weren't installed]
How about installing links as /etc/rc?.d/K??foo - so the links are there and
are properly manageable, but the init script will only be called as 'K??foo
stop'
-- vbi
--
Segunda le
On Thu, Dec 16, 2004 at 12:34:21AM +0100, Nicolas Boullis wrote:
> But a user felt concerned that, in the future, he may remove the package
> and forget to delete the links. Then I thought I could remove the links
> in postrm on purge, considering they are part of the package's
> configuration (
I wrote:
> Your script should check $PRERUNLEVEL. It will be N if you are booting.
That should be $PREVLEVEL.
--
John Hasler
Nicolas writes:
> I already thought about it, but I fnind it quite confusing when I cannot
> run /etc/init.d/foobar by hand as soon as it is not enabled on startup.
Your script should check $PRERUNLEVEL. It will be N if you are booting.
--
John Hasler
Hi,
On Wed, Dec 15, 2004 at 04:33:49PM -0800, Russ Allbery wrote:
>
> A technique that I've used in packages with this issue is to install the
> rc*.d symlinks by default, but also have the init script check a file in
> /etc/default to see whether or not to actually start at boot. If you
> insta
Nicolas Boullis <[EMAIL PROTECTED]> writes:
> A package of mine installs an init script. But as the corresponding
> programs plays with the motherboard's chipset configuration, it is quite
> prone to break the system. So I chose not to install rc*.d symlinks by
> default.
A technique that I've us
Hi folks,
A package of mine installs an init script. But as the corresponding
programs plays with the motherboard's chipset configuration, it is quite
prone to break the system. So I chose not to install rc*.d symlinks by
default.
To make life easier for users, i explain in a README file how t
17 matches
Mail list logo
