On Thursday 13 January 2005 02:29, Will Lowe wrote:
> > It does exactly as suggested above:
> > * remove existing symlinks
> > * add stop with priority 0
> > * remember original priorities when enabling them later on
>
> ... but is not scriptable. I'm thinking of environments like a large
> number
> It does exactly as suggested above:
> * remove existing symlinks
> * add stop with priority 0
> * remember original priorities when enabling them later on
... but is not scriptable. I'm thinking of environments like a large
number of hosts managed with cfengine -- update-rc.d is a handy
one-lin
On Wed, 12 Jan 2005 23:55:03 +0100, Erik Schanze <[EMAIL PROTECTED]> wrote:
> Will Lowe <[EMAIL PROTECTED]>:
> > I'm thinking have "update-rc.d -f foo disable" do the same thing as
> > "update-rc.d -f foo remove && update-rc.d foo stop stop 0", and
> > clearly document this in the manual page, so t
Will Lowe <[EMAIL PROTECTED]>:
> Given that this comes up so often, is there a reason not to add an
> option to update-rc.d that does this? The problem here is that
> "remove" sounds like "disable this".
>
> I'm thinking have "update-rc.d -f foo disable" do the same thing as
> "update-rc.d -f foo
> > This is an excellent question for debian-user. Or Google.
>
> And a question which has been answered countless times and is even
Given that this comes up so often, is there a reason not to add an
option to update-rc.d that does this? The problem here is that
"remove" sounds like "disable th
Hamish Moffatt wrote:
> Yes: don't remove ALL the links. If you keep some (eg all the K stop
> links), update-rc.d will not add any new ones.
I dunno, I've seen some strange things lately with bind9 and ipmasq
links that I'm quite sure were only disabled at rc2.d coming back on
upgrade. Not conclu
Scripsit Erik Schanze <[EMAIL PROTECTED]>
>> PS. this is a topic for debian-user not debian-devel
> Right, but I asked for a package for bug reporting.
That is, too, within debian-user's topic.
--
Henning Makholm "It will be useful even at this
On Wed, Jan 12, 2005 at 07:47:50PM +1100, Hamish Moffatt wrote:
> This is an excellent question for debian-user. Or Google.
And a question which has been answered countless times and is even
documented already (besides the manpage itself) at
http://www.debian.org/doc/manuals/securing-debian-howt
Hi Michal!
Michal Politowski <[EMAIL PROTECTED]>:
> On Wed, 12 Jan 2005 09:41:34 +0100, Erik Schanze wrote:
> > As I understand, deleting start links with 'update-rc.d -f apache remove'
> > is the Debian way of removing start calls for services at boot time.
>
> No. Generally update-rc.d is a tool
On Wed, 12 Jan 2005 09:41:34 +0100, Erik Schanze wrote:
> As I understand, deleting start links with 'update-rc.d -f apache remove' is
> the Debian way of removing start calls for services at boot time.
No. Generally update-rc.d is a tool for maintainer scripts not for the admin to
use.
Its man
On Wed, Jan 12, 2005 at 09:41:34AM +0100, Erik Schanze wrote:
> As I understand, deleting start links with 'update-rc.d -f apache remove' is
> the Debian way of removing start calls for services at boot time.
>
> After every package upgrade of e. g. apache, I must call this command again,
> beca
Hello!
As I understand, deleting start links with 'update-rc.d -f apache remove' is
the Debian way of removing start calls for services at boot time.
After every package upgrade of e. g. apache, I must call this command again,
because start links were be installed again. Is it the normal behavi
12 matches
Mail list logo
