On Thu, Dec 9, 2010 at 10:26 PM, Sven Joachim wrote:
> On 2010-12-09 18:55 +0100, Camaleón wrote:
>
>> I basically see two issues here:
>>
>> 1/ We lack? for a "recommended way/Debian way" for disabling scripts
>> (this thread is plenty of alternatives and tips for doing it but
>> documentation is
Sven Joachim wrote:
> Tom H wrote:
> > It's safer to use insserv's override mechanism.
>
> It's also more convenient. If you edit the script itself, dpkg will
> pester you with its conffile prompt every time the maintainer changes
> something in the script.
In my case that pestering is a feature
On 2010-12-09 18:55 +0100, Camaleón wrote:
> I basically see two issues here:
>
> 1/ We lack? for a "recommended way/Debian way" for disabling scripts
> (this thread is plenty of alternatives and tips for doing it but
> documentation is not very clear on the matter). I think it is important
> f
On Thu, Dec 09, 2010 at 04:50:52AM -0500, Tom H wrote:
> On Thu, Dec 9, 2010 at 2:56 AM, Joel Roth wrote:
> > On Wed, Dec 08, 2010 at 08:24:51PM +0100, Sven Joachim wrote:
> >> On 2010-12-07 17:21 +0100, Camaleón wrote:
>
>
> >> > A month ago, I disabled Network Manager service in my Squeeze sys
On Fri, 10 Dec 2010 01:33:20 +0900, Osamu Aoki wrote:
> On Thu, Dec 09, 2010 at 08:15:08AM +, Camaleón wrote:
>> On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
>>
>> > On 2010-12-08 23:41 +0100, Javier Barroso wrote:
>> >
>> >> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
>>
Hi,
On Thu, Dec 09, 2010 at 08:15:08AM +, Camaleón wrote:
> On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
>
> > On 2010-12-08 23:41 +0100, Javier Barroso wrote:
> >
> >> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
> >>>
> >>> You should use "update-rc.d network-manager disa
Sven Joachim wrote:
On 2010-12-09 09:15 +0100, Camaleón wrote:
On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
On 2010-12-08 23:41 +0100, Javier Barroso wrote:
On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
You should use "update-rc.d network-manager disable" instead. See
upd
On Thu, 09 Dec 2010 07:07:11 -0500, Tom H wrote:
> On Thu, Dec 9, 2010 at 6:11 AM, Camaleón wrote:
(...)
>> The warning can be ignored but the service levels are not touched and
>> it does not work as expected (meaning, the service is not disabled at
>> all).
>
> It was silly of me to say that
On Thu, Dec 9, 2010 at 6:11 AM, Camaleón wrote:
> On Thu, 09 Dec 2010 03:54:11 -0500, Tom H wrote:
>> On Wed, Dec 8, 2010 at 10:38 AM, Camaleón wrote:
>>
>> Whenever I use update-rc.d on a sid box to stop/remove/disable, I get a
>> "using concurrency based boot sequencing" message with a warning a
On Thu, 09 Dec 2010 03:54:11 -0500, Tom H wrote:
> On Wed, Dec 8, 2010 at 10:38 AM, Camaleón wrote:
(...)
>> Mmm... man page says by using "defaults" the service should be put in
>> sequence number 20 (unless there are any conflicts):
>>
>> t...@debian:~$ ls -l /etc/rc* | grep network-manager
>
On 2010-12-09 09:59 +0100, Tom H wrote:
> Even though someone posted earlier in this thread that updates respect
> editing "/etc/init.d" files, I'm not convinced that all packages
> behave that way.
Every package that does not is RC-buggy; I don't think there are many
such bugs.
> It's safer to
On Thu, Dec 9, 2010 at 2:56 AM, Joel Roth wrote:
> On Wed, Dec 08, 2010 at 08:24:51PM +0100, Sven Joachim wrote:
>> On 2010-12-07 17:21 +0100, Camaleón wrote:
>> > A month ago, I disabled Network Manager service in my Squeeze system so
>> > it doesn't run on start up. I wanted to keep NM install
On Wed, Dec 8, 2010 at 5:41 PM, Javier Barroso wrote:
> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
>> On 2010-12-07 17:21 +0100, Camaleón wrote:
>>
>>
>>> A month ago, I disabled Network Manager service in my Squeeze system so
>>> it doesn't run on start up. I wanted to keep NM installed
On Wed, Dec 8, 2010 at 5:19 PM, Arthur Machlas wrote:
> The move to insserv & lsb headers to deal with concurrent boot issues
> has thrown a bit of dust into the eyes of update-rc.d. I think if the
> user is working on a concurrent boot system, as squeeze is, they ought
> to consider handling sc
On 2010-12-09 09:15 +0100, Camaleón wrote:
> On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
>
>> On 2010-12-08 23:41 +0100, Javier Barroso wrote:
>>
>>> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
You should use "update-rc.d network-manager disable" instead. See
u
On Wed, Dec 8, 2010 at 4:43 PM, Camaleón wrote:
>
> In fact, what this thread has shown us is that there is not a standard
> method (let's call it "a common way") for doing a simple task like is
> disabling a script from running and keep its current status.
>
> I was looking for a "Debian way" for
On Wed, Dec 8, 2010 at 2:29 PM, shawn wilson wrote:
>
> You could always just remove the symlink under the rc#.d directory that you
> want to start (S) or stop (K) the service in.
>
> It's generally advised that you use update-rc.d to do this. However, IIRC
> this is the exact same thing that the
On Wed, Dec 8, 2010 at 2:14 PM, Arthur Machlas wrote:
> On Wed, Dec 8, 2010 at 9:21 AM, Camaleón wrote:
>> On Tue, 07 Dec 2010 17:09:14 -0600, Preston Boyington wrote:
>>> Camaleón wrote:
I agree this is the most common place to set the desired variable
values for the daemon and ev
On Wed, Dec 8, 2010 at 10:38 AM, Camaleón wrote:
> On Wed, 08 Dec 2010 08:37:52 -0500, Tom H wrote:
>> On Wed, Dec 8, 2010 at 8:23 AM, Camaleón wrote:
>>> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
>
You didn't disable network-manager. You removed the startup scripts
which
On 2010-12-08 01:21 +0100, Arthur Machlas wrote:
> Problem is, or at least, what I think the problem with that is, is
> that insserv is installed by default, and concurrent is now the
> default as well. So whenever a system service is added removed,
> changed or when insserv is called by some othe
On Thu, 09 Dec 2010 07:37:19 +0100, Sven Joachim wrote:
> On 2010-12-08 23:41 +0100, Javier Barroso wrote:
>
>> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
>>>
>>> You should use "update-rc.d network-manager disable" instead. See
>>> update-rc.d(8).
>> I think update-rc.d manpage should
On Wed, Dec 08, 2010 at 08:24:51PM +0100, Sven Joachim wrote:
> On 2010-12-07 17:21 +0100, Camaleón wrote:
>
>
> > A month ago, I disabled Network Manager service in my Squeeze system so
> > it doesn't run on start up. I wanted to keep NM installed (just in case)
> > but preferred to use the ol
On 2010-12-08 23:41 +0100, Javier Barroso wrote:
> On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
>>
>> You should use "update-rc.d network-manager disable" instead. See
>> update-rc.d(8).
> I think update-rc.d manpage should then change example which Camaleon
> referenced in her solved pos
Camaleón wrote:
> In fact, what this thread has shown us is that there is not a standard
> method (let's call it "a common way") for doing a simple task like is
> disabling a script from running and keep its current status.
>
> I was looking for a "Debian way" for handling this, not just with Ne
On Wed, Dec 8, 2010 at 8:24 PM, Sven Joachim wrote:
> On 2010-12-07 17:21 +0100, Camaleón wrote:
>
>
>> A month ago, I disabled Network Manager service in my Squeeze system so
>> it doesn't run on start up. I wanted to keep NM installed (just in case)
>> but preferred to use the old "ifup" network
First, apologies to Shawn. I didn't pay attention when responding.
Time to have dinner I think.
On Wed, Dec 8, 2010 at 3:56 PM, shawn wilson wrote:
>
>
> On Wed, Dec 8, 2010 at 4:43 PM, Camaleón wrote:
>>
>> On Wed, 08 Dec 2010 13:35:25 -0700, Bob Proulx wrote:
>>
>> > shawn wilson wrote:
>> >>
On Wed, Dec 8, 2010 at 4:43 PM, Camaleón wrote:
> On Wed, 08 Dec 2010 13:35:25 -0700, Bob Proulx wrote:
>
> > shawn wilson wrote:
> >> It's generally advised that you use update-rc.d to do this. However,
> >> IIRC this is the exact same thing that the command does (nothing more)
> >> so you shoul
On Wed, 08 Dec 2010 13:35:25 -0700, Bob Proulx wrote:
> shawn wilson wrote:
>> It's generally advised that you use update-rc.d to do this. However,
>> IIRC this is the exact same thing that the command does (nothing more)
>> so you should be fine.
>
> I see a lot of advice to use update-rc.d to m
shawn wilson wrote:
> It's generally advised that you use update-rc.d to do this. However, IIRC
> this is the exact same thing that the command does (nothing more) so you
> should be fine.
I see a lot of advice to use update-rc.d to manipulate the symlinks.
That is fine. But it isn't required. I
You could always just remove the symlink under the rc#.d directory that you
want to start (S) or stop (K) the service in.
It's generally advised that you use update-rc.d to do this. However, IIRC
this is the exact same thing that the command does (nothing more) so you
should be fine.
On 2010-12-07 17:21 +0100, Camaleón wrote:
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued "update-rc.d network-manage
On Wed, Dec 8, 2010 at 9:21 AM, Camaleón wrote:
> On Tue, 07 Dec 2010 17:09:14 -0600, Preston Boyington wrote:
>
>> Camaleón wrote:
>
>>> I agree this is the most common place to set the desired variable
>>> values for the daemon and even the easiest way to turn on/off a service
>>> at boot time b
On Tue, 07 Dec 2010 14:05:20 -0700, green wrote:
> Camaleón wrote at 2010-12-07 09:21 -0700:
>> So I issued "update-rc.d network-manager remove" and also disabled
>> gnome NM applet from being started. So far so good, no more NM running
>> at booting.
>
> You probably want to use "disable" instea
No one else has mentioned it:
chmod a-x /etc/init.d/script-name
Works for me :-)
Cheers
--
Joel Roth
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2010120816115
On Tue, 07 Dec 2010 15:46:50 -0700, Bob Proulx wrote:
> Arthur Machlas wrote:
>> Camaleón wrote:
>> > Are you suggesting to manually edit the "/etc/init.d/network-manager"
>> > script header to fit my needs? Correct me if I'm wrong, but I expect
>> > this file (as any file located here) can be upd
On Wed, 08 Dec 2010 08:37:52 -0500, Tom H wrote:
> On Wed, Dec 8, 2010 at 8:23 AM, Camaleón wrote:
>> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
(...)
>>> You didn't disable network-manager. You removed the startup scripts
>>> which were correctly put back by the update.
>>>
>>> O
On Tue, 07 Dec 2010 17:09:14 -0600, Preston Boyington wrote:
> Camaleón wrote:
>> I agree this is the most common place to set the desired variable
>> values for the daemon and even the easiest way to turn on/off a service
>> at boot time but the thing is that there is not such file for Network
On Wed, Dec 8, 2010 at 8:23 AM, Camaleón wrote:
> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
> On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
>> On Tue, Dec 07, 2010 at 04:21:38PM +, Camale?n wrote:
>>>
>>> A month ago, I disabled Network Manager service in my Squeeze s
On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
On Tue, 07 Dec 2010 23:46:53 +0100, Jochem Kossen wrote:
> On Tue, Dec 07, 2010 at 04:21:38PM +, Camale?n wrote:
>> Hello,
>>
>> A month ago, I disabled Network Manager service in my Squeeze system so
>> it doesn't run on start up. I w
On Tue, Dec 7, 2010 at 2:35 PM, Camaleón wrote:
> On Tue, 07 Dec 2010 10:51:11 -0600, Arthur Machlas wrote:
>>
>> I'd definitely hold off on the bug report. I think you should look at
>> the lsb headers of the network-manager script in /etc/init.d and change
>> them to stop on all levels, start on
On Tue, Dec 7, 2010 at 6:16 PM, Paul Lane wrote:
> On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
>> Hello,
>>
>> A month ago, I disabled Network Manager service in my Squeeze system so
>> it doesn't run on start up. I wanted to keep NM installed (just in case)
>> but preferred to use the old "
On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
> Hello,
>
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued "update-rc.d
On Tue, Dec 07, 2010 at 04:21:38PM +, Camale?n wrote:
> Hello,
>
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued
Camaleón wrote:
On Tue, 07 Dec 2010 08:49:03 -0800, Mike wrote:
"update-rc.d network-manager remove"
I don't have this service, but generally I'd expect to disable a service
through its /etc/default/ settings.
I agree this is the most common place to set the desired variable values
for the
Arthur Machlas wrote:
> Camaleón wrote:
> > Are you suggesting to manually edit the "/etc/init.d/network-manager"
> > script header to fit my needs? Correct me if I'm wrong, but I expect this
> > file (as any file located here) can be updated at any time and so
> > replacing any of the customized v
Camaleón wrote at 2010-12-07 09:21 -0700:
> So I issued "update-rc.d network-manager remove" and also disabled gnome
> NM applet from being started. So far so good, no more NM running at
> booting.
You probably want to use "disable" instead of "remove". See update-rc.d(8).
signature.asc
Descr
On Tue, Dec 7, 2010 at 1:35 PM, Camaleón wrote:
> On Tue, 07 Dec 2010 10:51:11 -0600, Arthur Machlas wrote:
>
>> On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
>
> (...)
>
>>> Before I fill a bug report (I think a service that has been manually
>>> disabled should keep its state regardless any f
On Tue, 07 Dec 2010 10:51:11 -0600, Arthur Machlas wrote:
> On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
(...)
>> Before I fill a bug report (I think a service that has been manually
>> disabled should keep its state regardless any further update it can be
>> applied afterwards), I would lik
On Tue, 07 Dec 2010 08:49:03 -0800, Mike wrote:
>> "update-rc.d network-manager remove"
>
> I don't have this service, but generally I'd expect to disable a service
> through its /etc/default/ settings.
I agree this is the most common place to set the desired variable values
for the daemon and
On Tue, Dec 7, 2010 at 10:21 AM, Camaleón wrote:
> Hello,
Hi
> A month ago, I disabled Network Manager service in my Squeeze system so
> it doesn't run on start up. I wanted to keep NM installed (just in case)
> but preferred to use the old "ifup" network setup method.
>
> So I issued "update-rc
> "update-rc.d network-manager remove"
I don't have this service, but generally I'd expect to disable a
service through its /etc/default/ settings.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Arc
Hello,
A month ago, I disabled Network Manager service in my Squeeze system so
it doesn't run on start up. I wanted to keep NM installed (just in case)
but preferred to use the old "ifup" network setup method.
So I issued "update-rc.d network-manager remove" and also disabled gnome
NM applet f
52 matches
Mail list logo
