On Sun, Nov 12, 2000 at 02:36:24PM -0200, Henrique M Holschuh wrote:
> + `restart-if-running'
> + stop the service, and if the service was running before being
> + stopped by restart-if-running, restart it,
I have a question about this part. Are we planning to assume that all
scripts in init.d support this argument? If so, we may be in trouble
when it comes to locally installed scripts. If not, then the utility
seems fairly small.
It seems like there are really two proposals here, bundled as one.
The invoke-rc.d seems like a fine idea, but I'm less sure about
restart-if-running. Can we split this into two proposals, or is there
some reason that they're tied together which I'm missing?
Personally, when I wear my sysadmin hat, I'm quite aware of the fact
that things I've started or stopped manually may get restarted/
restopped by an update, and I always take measures if this is likely
to cause problems. I would assume that anyone who knows how to muck
about with the init.d scripts in the first place would have some idea
of what's going on. I suspect that the "user who has stopped a
process, and isn't aware that updating its package may restart it" is
a mythical beast.
The init.d scripts are conffiles, yes? (I hope they are; I've always
treated them as if they are.) That means that you can't rely on the
presence of a new target even if you put it there yourself (the user
may have chosen "already installed version" when updating the package.)
So, well, bottom line, I definitely support invoke-rc.d, but I'd like
to know more before supporting restart-if-running.
Chris Waters firstname.lastname@example.org | I have a truly elegant proof of the
or email@example.com | above, but it is too long to fit into
| this .signature file.
- From: Henrique M Holschuh <firstname.lastname@example.org>
- From: Anthony Towns <email@example.com>