Am 07.05.21 um 02:12 schrieb Michael Biebl:
exim4 is unfortunately still SysV-only and doesn't ship a native systemd
.service file. So the correct command is
"update-rc.d exim4 disable"
For the curious: you can run "systemctl disable exim4" as well.
This will just run
exim4 is unfortunately still SysV-only and doesn't ship a native systemd
.service file. So the correct command is
"update-rc.d exim4 disable"
"update-rc.d exim4 remove" will remove the symlinks in /etc/rc?.d/ but on
the next package update, they will be recreated.
So i
t; at boot time, and applies to all the init.d scripts that systemd sees.
> > Doing a "disable" after this would only affect the generated services,
> > which are ephemeral and go away when you reboot.
>
> As far as I recall (but it's been a while since I neede
this would only affect the generated services,
> which are ephemeral and go away when you reboot.
As far as I recall (but it's been a while since I needed this)
update-rc.d is the correct tool and it should even take care of
synchronizing state between systemd and sysv-rc.
> To permanen
boot time, and applies to all the init.d scripts that systemd sees.
Doing a "disable" after this would only affect the generated services,
which are ephemeral and go away when you reboot.
To permanently disable the starting of this service, you'll need to
use the actual sysv-rc techniques (either removing or renaming symlinks,
or using Debian's weird update-rc.d tool which relies on parsing comments
inside the init.d script).
On Tue, 4 May 2021 18:44:12 -0400
Greg Wooledge wrote:
> On Tue, May 04, 2021 at 10:14:45PM +0100, Joe wrote:
> > ...and buster. It's exim4.service as stated by:
> > systemctl --type=service | grep exim
>
> According to packages.debian.org[1] there is no such file in any
> package.
>
> Of co
On Tue, May 04, 2021 at 10:14:45PM +0100, Joe wrote:
> ...and buster. It's exim4.service as stated by:
> systemctl --type=service | grep exim
According to packages.debian.org[1] there is no such file in any
package.
Of course, that's not proof of the nonexistence of such a file, because
it might
On Tue, 4 May 2021 18:27:57 +0100
Joe wrote:
> On Tue, 4 May 2021 13:15:51 -0400
> Greg Wooledge wrote:
>
> > On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> > > That was the question, Greg:
> > >
> > > "Searching for exim in
> > > /etc/systemd/system/multi-user.targe
On Tue, May 04, 2021 at 01:46:29PM -0700, John Conover wrote:
>
> Try:
>
> man update-rc.d
> man 8 update-rc.d
>
Please stop top-posting, and please reply to the list.
> Greg Wooledge writes:
> > On Tue, May 04, 2021 at 01:27:56PM -0700, John Conover wrote
On Tue, May 04, 2021 at 01:27:56PM -0700, John Conover wrote:
> As per the man page for System V init, to disable launching of exim:
>
> update-rc.d -f exim remove
What man page is this allegedly from, exactly?
uring boot by policy.
As per the man page for System V init, to disable launching of exim:
update-rc.d -f exim remove
which would be (re-)enabled with:
update-rc.d -f exim defaults
which installs the ln -s files in /etc/rc*.d, as appropriate.
The correct command on Buster is:
update
On 5/4/2021 7:28 PM, Erwan David wrote:
Le 04/05/2021 à 19:26, Joe a écrit :
On Tue, 4 May 2021 10:03:43 -0700
cono...@rahul.net (John Conover) wrote:
Greg Wooledge writes:
On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
Searching for exim in
/etc/systemd/system/multi-user.targ
On Tue, May 04, 2021 at 10:27:17AM -0700, John Conover wrote:
>
> Thanks, Greg. "update-rc.d -f exim remove" is the command for
> /etc/init.d. But its broken.
You forgot to reply to the list.
Nobody with any sense uses update-rc.d for system admin work. It's
there fo
Le 04/05/2021 à 19:26, Joe a écrit :
> On Tue, 4 May 2021 10:03:43 -0700
> cono...@rahul.net (John Conover) wrote:
>
>> Greg Wooledge writes:
>>> On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
Searching for exim in
/etc/systemd/system/multi-user.target.wants/* and
/l
On Tue, 4 May 2021 13:15:51 -0400
Greg Wooledge wrote:
> On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> > That was the question, Greg:
> >
> > "Searching for exim in
> > /etc/systemd/system/multi-user.target.wants/* and
> > /lib/systemd/system/* yields nothing."
> >
On Tue, 4 May 2021 10:03:43 -0700
cono...@rahul.net (John Conover) wrote:
> Greg Wooledge writes:
> > On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> > > Searching for exim in
> > > /etc/systemd/system/multi-user.target.wants/* and
> > > /lib/systemd/system/* yields nothing.
> >
On Tue, May 04, 2021 at 10:03:43AM -0700, John Conover wrote:
> That was the question, Greg:
>
> "Searching for exim in
> /etc/systemd/system/multi-user.target.wants/* and
> /lib/systemd/system/* yields nothing."
>
> so, it wasn't there. Which service?, (or how to find out?)
So... I
Greg Wooledge writes:
> On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> > Searching for exim in /etc/systemd/system/multi-user.target.wants/*
> > and /lib/systemd/system/* yields nothing.
> >
> > How do I stop exim from launching across boots?
>
> Presumably there is a systemd ser
On Tue, May 04, 2021 at 09:17:38AM -0700, John Conover wrote:
> Searching for exim in /etc/systemd/system/multi-user.target.wants/*
> and /lib/systemd/system/* yields nothing.
>
> How do I stop exim from launching across boots?
Presumably there is a systemd service, which is enabled. You will wa
I use either exim or another MTA. When I want to use the other MTA,
"update-rc.d -f exim remove" does not remove exim from "ps eax" after
today's exim update.
Searching for exim in /etc/systemd/system/multi-user.target.wants/*
and /lib/systemd/system/* yields nothing.
update-rc.d my-program defaults 20 80
update-rc.d my-program defaults start 20 2 3 4 5 . stop 80 0 1 6 .
Support for run levels in "start" and "stop" subcommands was dropped
from update-rc.d by Roger Leigh in 2013. You'll find that the command
has been warning you
;.
>>
>
> Many thanks for the correction, which seems to have fixed my execution
> problems.
[...]
> , command
> update-rc.d my-program defaults 20 80
> gives the correct orders of my-program and postgresql like so:
You can leave out the numbers at the end, that is just
2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: My program.
# Description: My program.
### END INIT INFO
, command
update-rc.d my-program defaults 20 80
gives the correct orders of my-program and postgresql like so:
S02postgresql
S03my-program
and
K02my-program
K03postgresql
I think th
Hi,
CN writes:
> /etc/init.d/my-program is correctly prepared with LSB header comments
> like this:
>
> #!/bin/sh
> ### BEGIN INIT INFO
> # Provides: my-program
> # Required-Start: $postgresql
> # Required-Stop:$postgresql
> # Default-Start:2 3 4 5
> # Default-St
f
> > the parent package that held this file too. No use comparing apples
> > to tangerines. :)
>
> Gene, you have me confused now. This is *exactly* what we did: we
> compared the version of the package containing update-rc.d and the
> program file's sha1sum. Both mat
Am 13.05.2016 um 16:16 schrieb CN:
> On Fri, May 13, 2016, at 09:14 PM, to...@tuxteam.de wrote:
>> Jessie/Sid here. But the more important thing is... what version of
>> sysv-rc is yours? What update-rc.d are you using?
>>
>
> "dpkg -l sysv-rc" show
held this file too. No use comparing apples to
> tangerines. :)
Gene, you have me confused now. This is *exactly* what we did: we compared
the version of the package containing update-rc.d and the program file's
sha1sum. Both match.
We still get different behaviours, thus there must be somet
On Friday 13 May 2016 10:16:00 CN wrote:
> On Fri, May 13, 2016, at 09:14 PM, to...@tuxteam.de wrote:
> > Jessie/Sid here. But the more important thing is... what version of
> > sysv-rc is yours? What update-rc.d are you using?
>
> "dpkg -l sysv-rc" show this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, May 13, 2016 at 10:16:00PM +0800, CN wrote:
> On Fri, May 13, 2016, at 09:14 PM, to...@tuxteam.de wrote:
> > Jessie/Sid here. But the more important thing is... what version of
> > sysv-rc is yours? What update-rc.
On Fri, May 13, 2016, at 09:14 PM, to...@tuxteam.de wrote:
> Jessie/Sid here. But the more important thing is... what version of
> sysv-rc is yours? What update-rc.d are you using?
>
"dpkg -l sysv-rc" show this from local host:
ii sysv-rc2.88dsf-41+deb7u1
"
dsf-41+deb7u1
> >
> > What version is yours? And... just to double-check:
> >
> > tomas@rasputin:~$ sha1sum /usr/sbin/update-rc.d
> > 19d097b7dbe7f0d0a551e40e9183656f81908088 /usr/sbin/update-rc.d
> >
> > (pity that it hasn't --version and --debu
On Fri, May 13, 2016, at 08:46 PM, to...@tuxteam.de wrote:
>
> Bizarre. Just tried in my box and it behaves as it should. It comes from
>
> sysv-rc 2.88dsf-41+deb7u1
>
> What version is yours? And... just to double-check:
>
> tomas@rasputin:~$ sha1s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, May 13, 2016 at 07:54:55PM +0800, CN wrote:
> Hi!
[...]
> Both of these two commands
>
> update-rc.d my-program defaults 20 80
> update-rc.d my-program defaults start 20 2 3 4 5 . stop 80 0 1 6 .
>
> yield the sa
: My program.
# Description: My program.
### END INIT INFO
Both of these two commands
update-rc.d my-program defaults 20 80
update-rc.d my-program defaults start 20 2 3 4 5 . stop 80 0 1 6 .
yield the same incorrect sequence numbers in contrast to the results
demonstrated here:
https://debian
> > But after next boot, it does not work any more - I have to to
> > dpkg-reconfigure again.
>
> Do you have a symlink /etc/rcS.d/S??eeepc-acpi-scripts pointing to
> ../init.d/eeepc-acpi-scripts (the exact value of ?? varies from system
> to system)?
>
> Also, which init system do you use?
>
>
On 2014-06-22 11:36 +0200, Hans wrote:
> Hello list,
> after changing to systemd some packages give me the following message:
>
> warning: update-rc.d: warning: start and stop actions are no longer
> supported;
> falling back to defaults
This message is harmless, the star
Hello list,
after changing to systemd some packages give me the following message:
warning: update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
It also looks like, these demons are no more started at boot. For example,
eeepc-acpi-scripts gives such a
François Patte wrote:
> While installing some packages, I get this message:
>
> update-rc.d: warning: start and stop actions are no longer supported;
> falling back to defaults
>
> What does it mean?
Sid Unstable and Jessie Testing have moved on past hard listed boot
number
On Tue, 2013-08-20 at 09:42 +0200, François Patte wrote:
> Le 18/08/2013 12:37, Ralf Mardorf a écrit :
> > On Sun, 2013-08-18 at 12:35 +0200, Ralf Mardorf wrote:
> >> On Sun, 2013-08-18 at 12:26 +0200, François Patte wrote:
> >>> update-rc.d: warning: start and stop a
On Sun, 2013-08-18 at 12:35 +0200, Ralf Mardorf wrote:
> On Sun, 2013-08-18 at 12:26 +0200, François Patte wrote:
> > update-rc.d: warning: start and stop actions are no longer supported;
> > falling back to defaults
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=7175
On Sun, 2013-08-18 at 12:26 +0200, François Patte wrote:
> update-rc.d: warning: start and stop actions are no longer supported;
> falling back to defaults
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717553
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a s
Bonjour,
While installing some packages, I get this message:
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
What does it mean?
Thank you
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris
Art Huston wrote:
> I added /etc/init.d/tightvncserver to start a VNC server. It looks fine --
> I have the LSB comments and it works when invoked directly from the
> command-line, e.g.
>
> cd /etc/init.d
> ./tightvncserver start
>
> But update-rc.d gives an error:
>
Hi,
I added /etc/init.d/tightvncserver to start a VNC server. It looks fine --
I have the LSB comments and it works when invoked directly from the
command-line, e.g.
cd /etc/init.d
./tightvncserver start
But update-rc.d gives an error:
root@debian01:/etc/init.d# update-rc.d tightvncserver
Sven Joachim wrote:
On 2010-06-02 18:28 +0200, Hugo Vanwoerkom wrote:
Before dependency based boot I added my own boot scripts with
update-rc.d, like:
update-rc.d faketty start 29 2 3 4 5 .
and the update-rc.d man page still refers to sequence numbers (NN=29):
"NN is the two-digit seq
On 2010-06-02 18:28 +0200, Hugo Vanwoerkom wrote:
> Before dependency based boot I added my own boot scripts with
> update-rc.d, like:
>
> update-rc.d faketty start 29 2 3 4 5 .
>
> and the update-rc.d man page still refers to sequence numbers (NN=29):
>
> "NN is
Jordan Metzmeier wrote:
On 06/02/2010 12:28 PM, Hugo Vanwoerkom wrote:
Hi,
Before dependency based boot I added my own boot scripts with
update-rc.d, like:
update-rc.d faketty start 29 2 3 4 5 .
and the update-rc.d man page still refers to sequence numbers (NN=29):
"NN is the two-
On 06/02/2010 12:28 PM, Hugo Vanwoerkom wrote:
Hi,
Before dependency based boot I added my own boot scripts with
update-rc.d, like:
update-rc.d faketty start 29 2 3 4 5 .
and the update-rc.d man page still refers to sequence numbers (NN=29):
"NN is the two-digit sequence number
Hi,
Before dependency based boot I added my own boot scripts with
update-rc.d, like:
update-rc.d faketty start 29 2 3 4 5 .
and the update-rc.d man page still refers to sequence numbers (NN=29):
"NN is the two-digit sequence number that determines where in the
sequence init will ru
rwrites defaults (empty).
>
> Is it safe for the system administrator to issue
>
> update-rc.d remove defaults ntp
> update-rc.d remove start 20 2 3 4 5 . stop 20 0 1 6 . ntp
>
> ? That is, will such commands break something?
>
> Some references are bugs 56897
As some of you might know, the transition to dependency based
boot / insserv is causing the following lines:
insserv: warning: current stop runlevel(s) (0 1 6) of script `ntp'
overwrites defaults (empty).
Is it safe for the system administrator to issue
update-rc.d r
On Sun, Jun 25, 2006 at 11:21:01AM EDT, Willie Wonka wrote:
[...]
>
> ~$ locate rcconf
> and nothing returns, until I update the DataBase
>
> ~$ sudo updatedb
> and now the updating occurs (and takes 2-5 minutes :-(, even on this small
> installation and small HD).
>
> now the 'locate' command
n connection with system
runlevels. It turns on/off services using the scripts in
/etc/init.d/. Rcconf works with System-V style runlevel configuration.
It is a TUI (Text User Interface) frontend to the update-rc.d command.
so, I try and see if it's a
From: "iforone" <[EMAIL PROTECTED]>
Newsgroups: linux.debian.user
Subject: Re: update-rc.d questions: best practice?
Date: Wed, 01 Mar 2006 20:49:42 -0800
Ivan Teliatnikov wrote:
> Hi everyone.
> [...]
> 2. Is there a command/tool to display status of all
services in
L.V.Gandhi wrote:
> which package has update-rc.d
It's in sysv-rc. It's a required package, so you have it.
I suggest that you look at the sysvconfig package, though.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
On Wed, 1 Mar 2006 16:14:46 -0800
L.V.Gandhi <[EMAIL PROTECTED]> wrote:
> On 3/1/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
>
> > update-rc.d defaults
>
> which package has update-rc.d
I honestly don't know, its in the minimal sys
On 3/1/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
> update-rc.d defaults
which package has update-rc.d
--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042
On Wed, 01 Mar 2006 23:35:03 +1100
Ivan Teliatnikov <[EMAIL PROTECTED]> wrote:
> Hi everyone.
>
> I am pursing a task of establishing a procedure among my colleagues -
> system administrator which will help us enable/disable services on
> Debian servers.
>
> I
Ivan Teliatnikov writes:
> Is there a command/tool to display status of all services in all
> runlevels.
I suggest that you install sysvconfig. It will do most or all of what you
need.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
On Wed, 01 Mar 2006 17:57:55 +1100
Ivan Teliatnikov <[EMAIL PROTECTED]> wrote:
> Hi everyone.
>
> I am pursing a task of establishing a procedure among my colleagues -
> system administrator which will help us enable/disable services on
> Debian servers.
>
> I
Hi everyone.
I am pursing a task of establishing a procedure among my colleagues -
system administrator which will help us enable/disable services on
Debian servers.
I am considering "update-rc.d" script that is mentioned in Debian
documentation and was also mentioned on this lis
Hi everyone.
I am pursing a task of establishing a procedure among my colleagues -
system administrator which will help us enable/disable services on
Debian servers.
I am considering "update-rc.d" script that is mentioned in Debian
documentation and was also mentioned on this lis
On 11/5/05, Peter Valdemar Mørch <[EMAIL PROTECTED]> wrote:
Using Nessus as an example, I know how to disable it from startingautomatically with:# update-rc.d -f nessusd removeBut then, two weeks down the road, a new version of nessus comes along,and after a dist-upgrade, the service is s
Hi,
Peter Valdemar Mørch wrote:
> # update-rc.d -f nessusd remove
>
> But then, two weeks down the road, a new version of nessus comes along,
> and after a dist-upgrade, the service is started automatically again,
> because the nessus package calls update-rc.d to have the nessusd
On 05 Nov 2005, Peter Valdemar Mørch wrote:
> Using Nessus as an example, I know how to disable it from starting
> automatically with:
> # update-rc.d -f nessusd remove
>
> But then, two weeks down the road, a new version of nessus comes along,
> and after a dist-upgrade, the
Using Nessus as an example, I know how to disable it from starting
automatically with:
# update-rc.d -f nessusd remove
But then, two weeks down the road, a new version of nessus comes along,
and after a dist-upgrade, the service is started automatically again,
because the nessus package calls
On Sat, 10 Jul 2004 03:34:22 +0100, Thomas Adam wrote:
>> what is the right way to specify a service that only has start but no
>> stop?
>
> station:~# update-rc.d local start 80 2 3 4 5 .
> Adding system startup for /etc/init.d/local ...
>/etc/rc2.d/S80local ->
--- * Tong* <[EMAIL PROTECTED]> wrote:
> what is the right way to specify a service that only has start but no
> stop?
station:~# update-rc.d local start 80 2 3 4 5 .
Adding system startup for /etc/init.d/local ...
/etc/rc2.d/S80local -> ../init.d/local
/etc/rc3.d/S80loc
On Sat, 10 Jul 2004 01:25:07 +0100, Thomas Adam wrote:
>> # update-rc.d local defaults start 80
>> update-rc.d: error: codenumber must be a number between 0 and 99
>
> update-rc.d local defaults 80
Come on, Thomas, I notice that you seldom read people's posting closely
* Tong* wrote:
> Q: In RedHat, the chkconfig can also be used to generate a code
>skeleton that have start/stop, etc. Can we do it in debian?
update-rc.d would be the equivalent tool.
> Q: what is the right way to specify a service that
>only has start but no stop?
Make t
--- * Tong* <[EMAIL PROTECTED]> wrote:
>
> # update-rc.d local defaults start 80
> update-rc.d: error: codenumber must be a number between 0 and 99
update-rc.d local defaults 80
-- Thomas Adam
=
"The Linux Weekend Mechanic" -- http://linuxgazette.net
"TAG E
On Fri, 09 Jul 2004 23:44:07 +0100, Thomas Adam wrote:
>> % update-rc.d local defaults 80-start
>> update-rc.d: error: codenumber must be a number between 0 and 99
>> usage: update-rc.d [-n] [-f] remove
>>update-rc.d [-n] defaults [NN | sNN kNN]
>
> RTFM
--- * Tong* <[EMAIL PROTECTED]> wrote:
> % update-rc.d local defaults 80-start
> update-rc.d: error: codenumber must be a number between 0 and 99
> usage: update-rc.d [-n] [-f] remove
> update-rc.d [-n] defaults [NN | sNN kNN]
RTFM would help here. You're almos
Q: In RedHat, the chkconfig can also be used to generate a code
skeleton that have start/stop, etc. Can we do it in debian?
Q: what is the right way to specify a service that
only has start but no stop?
I just can't get it right. from the man page it is:
,-
| update-rc.d [-n]
martin f krafft writes:
> So what's the recommended way of disabling services?
I suggest sysvconfig.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, 21 Jun 2004, martin f krafft wrote:
> The recommended way to disable a service, or to move its
> initialisation priority is update-rc.d. However, when the package is
update-rc.d is for THE PACKAGING SYSTEM. It is not meant as an
admin tool. It could be made smarter, like dpkg-
I have not found a clean solution to this, so let me pester y'all...
The recommended way to disable a service, or to move its
initialisation priority is update-rc.d. However, when the package is
upgraded, it is likely that the choice I made for update-rc.d will
be overwritten. Since update
monique writes:
> Well, update-rc.d doesn't seem to be designed for tweaking settings once
> a package is installed, so what would you suggest?
Invoke-rc.d comes closer, but it isn't quite adequate either. Until it has
the necessary features added you pretty much have to do it al
On 2004-06-03, Miquel van Smoorenburg penned:
> In article <[EMAIL PROTECTED]>, Sebastian
> Kügler <[EMAIL PROTECTED]> wrote:
>>> It's probably easier to use `ln -s` than to get update-rc.d working
>>> as you would like.
>>
>>I am now usin
In article <[EMAIL PROTECTED]>,
Sebastian Kügler <[EMAIL PROTECTED]> wrote:
>> It's probably easier to use `ln -s` than to get update-rc.d working as
>> you would like.
>
>I am now using symlinking rather than update-rc.d, and it seems to work fine.
Sure,
On Wednesday 02 June 2004 21:40, Monique Y. Mudama wrote:
> On 2004-06-01, Sebastian Kügler penned:
> > 1) What would you recommend to create the symlinks in the various
> > runlevels, what is the preferred way of manipulating the runlevel stuff?
> > a)ln -s
> > b)upda
pulating the runlevel stuff?
> a)ln -s
> b)update-rc.d
>
> My first thought was to use the latter, but I encountered a problem, which
> lead to my next question.
>
> 2) If I remove all symlinks in all runlevels (basically "update-rc.d -f
> proftpd remove"), c
On Wed, Jun 02, 2004 at 01:16:08AM +0200, Sebastian Kügler wrote:
> Hi,
>
> I am in the course of writing a graphical runlevel editor, and I happen to
> have the following questions:
>
> 2) If I remove all symlinks in all runlevels (basically "update-rc.d -f
>
Hi,
I am in the course of writing a graphical runlevel editor, and I happen to
have the following questions:
1) What would you recommend to create the symlinks in the various runlevels,
what is the preferred way of manipulating the runlevel stuff?
a) ln -s
b) update-rc.d
My
Hello
T. Albert (<[EMAIL PROTECTED]>) wrote:
> what's the equivalence of chkconfig --list in debian using
> update-rc.d ? i have difficulties in listing what services are on on
> init level 3 for example. thank you.
ls -l /etc/rcS.d /etc/rc3.d
I don't
Hello debian-user,
what's the equivalence of chkconfig --list in debian using
update-rc.d ? i have difficulties in listing what services are on on
init level 3 for example. thank you.
--
Best regards,
Tjhan Albert
"The future belongs to those who believes in the beaut
In article <[EMAIL PROTECTED]>,
Miguel Alvarez Blanco <[EMAIL PROTECTED]> wrote:
>As I said in the first message, I do not know how to keep a package
>installed in the system and yet be able to de-activate its startup
>scripts, sort of like leaving it unconfigured.
# cd /etc/init.d
# mv script
wrote:
> Date: Wed, 12 Nov 2003 12:42:57 +0100
> From: Miguel Alvarez Blanco <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: update-rc.d
>
> Hi,
>
> I do not really know if this is a bug or a "feature", so I am not
> sending it as a bug report. T
hen leaving /etc/rc0.d/K99ipmasq and /etc/rc6.d/K99/ipmasq is
consistent with what you want, and still lets update-rc.d believe the
package is "installed".
IMHO the Debian system makes a lot of sense here, though it's not
perfect. Everybody knows how to use 'rm' and &
Henrique de Moraes Holschuh wrote:
update-rc.d is working as intended. Read its manpage about how you as the
local admin should interact with it.
In particular, update-rc.d is to be used ONLY by the packaging system, not
by the local admin.
Thanks for the quick response. However, I am not sure if
On Wed, 12 Nov 2003, Miguel Alvarez Blanco wrote:
> I do not really know if this is a bug or a "feature", so I am not
update-rc.d is working as intended. Read its manpage about how you as the
local admin should interact with it.
In particular, update-rc.d is to be used ONLY by
sing it to provide
net access to another machine while on a single-IP net connection, but I
no longer used it, so I just used update-rc.d to remove the links in
rcS.d and avoid it running at startup. I did not want to erase it, since
the machine is a laptop and I may need it again sometime (I pref
nce/examples/go-woody
For the most part this went well, and ran for a long time. One concern I had
was that util-linux was removed with a stern warning, and the upgrade continued
for a long time without it. I received periodic messages about being unable to
exec modprobe.
But then it stopped wit
On 30-Nov-2001 Oki DZ wrote:
> Hi,
>
> We can have update-rc.d -f remove to remove the daemon from
> the init script. Why can't we have update-rc.d -l to list
> the init levels in which the daemon will be started.
>
because debian by default does not mess with run le
On Fri, Nov 30, 2001 at 02:39:43PM +0700, Oki DZ wrote:
> We can have update-rc.d -f remove to remove the daemon from
> the init script. Why can't we have update-rc.d -l to list
> the init levels in which the daemon will be started.
$ ls -1 /etc/rc?.d/???ssh
This gives nice list f
Hi,
We can have update-rc.d -f remove to remove the daemon from
the init script. Why can't we have update-rc.d -l to list
the init levels in which the daemon will be started.
Oki
On Sat, Mar 27, 1999 at 09:35:27AM +0100, Piotr Legiecki wrote:
> Hi
> I'v received an answer to my question about managing links in rcx.d
> directories, but it wasn't what I was talking about.
> The update-rc.d scripts simply removes links AND scripts from init.d
>
>
> Hi
> I'v received an answer to my question about managing links in rcx.d
> directories, but it wasn't what I was talking about.
> The update-rc.d scripts simply removes links AND scripts from init.d
> directory and I want only temporarly disable
> running som
Hi
I'v received an answer to my question about managing links in rcx.d
directories, but it wasn't what I was talking about.
The update-rc.d scripts simply removes links AND scripts from init.d directory
and I want only temporarly disable
running some daemons during system startup (li
> - first of all, a major problem.
> /usr/sbin/update-rc.d doesn't work and then I don't have any /etc/rc?.d
> directory... It failed around line 270 with the message:
> "integer expression excepted" in the test:
>if [ "$START_SORT_NO&quo
1 - 100 of 104 matches
Mail list logo
