Hi,
Stephan Seitz writes:
> On Di, Okt 23, 2018 at 08:16:51 -0400, Hendrik Boom wrote:
>>On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
>>> Make that: "there *was* a command, chkconfig:"
>>>
>>> It's no longer present in Debian stable (stretch) and later. You can
>>> still
Le 23/10/2018 à 19:27, Steve Litt a écrit :
Vim or Emacs. You can only have one.
Perl, Python, Ruby or Lua. You can only have one.
Mutt or Thunderbird. You can only have one.
Sysvinit, runit, s6, perp or Epoch. You can only have one.
kernel, can you have two?
fstab, can you have
I think this is desired only if you want to enable both rc init
scripts and runit scripts on the same system, which, in my opinion is
not a sane configuration.
"Sane configuration."
Have you been talking to my psychiatrist again? I was involuntarily
committed in 2009 for running
On Sun, Oct 21, 2018 at 11:18:39PM +0200, Arnt Karlsen wrote:
> On Sun, 21 Oct 2018 19:07:36 +0200, Didier wrote in message
> <826ba68a-6289-d047-7e74-d970996d2...@in2p3.fr>:
>
> > Le 21/10/2018 à 19:01, Didier Kryn a écrit :
> > > I'm not an expert, but it seems to me the answer is in
On Tue, 23 Oct 2018 16:00:08 +0200
Didier Kryn wrote:
> Le 23/10/2018 à 15:45, Stephan Seitz a écrit :
> > On Di, Okt 23, 2018 at 08:16:51 -0400, Hendrik Boom wrote:
> >> On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
> >>> Make that: "there *was* a command, chkconfig:"
>
On Tue, 23 Oct 2018 16:00:08 +0200
Didier Kryn wrote:
> Le 23/10/2018 à 15:45, Stephan Seitz a écrit :
> > On Di, Okt 23, 2018 at 08:16:51 -0400, Hendrik Boom wrote:
> >> On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
> >>> Make that: "there *was* a command, chkconfig:"
>
>> As far as I know chkconfig was never a Debian tool. I only know it
>> from RPM distros. Maybe someone tried to include chkconfig in Debian,
>> but gave up later. Or it never really worked.
I frequently used (and liked) chkconfig because it did work well on Red
Hat Distros. I can see that
On Tue, 23 Oct 2018 15:45:19 +0200
Stephan Seitz wrote:
> On Di, Okt 23, 2018 at 08:16:51 -0400, Hendrik Boom wrote:
> >On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
> >> Make that: "there *was* a command, chkconfig:"
> >>
> >> It's no longer present in Debian stable
On 10/23/18 4:27 AM, Olaf Meeuwissen wrote:
Hi,
Bruce Ferrell writes:
[...]
If I understand the original question "how to I get sysV init to not
start a process present in the init system", There is a command,
chkconfig:
Make that: "there *was* a command, chkconfig:"
It's no longer present
Quoting Stephan Seitz (stse+dev...@fsing.rootsland.net):
> As far as I know chkconfig was never a Debian tool. I only know it
> from RPM distros. Maybe someone tried to include chkconfig in
> Debian, but gave up later. Or it never really worked.
It may be of interest that the Red Hat 'chkconfig'
Le 23/10/2018 à 15:45, Stephan Seitz a écrit :
On Di, Okt 23, 2018 at 08:16:51 -0400, Hendrik Boom wrote:
On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
Make that: "there *was* a command, chkconfig:"
It's no longer present in Debian stable (stretch) and later. You can
still
On Di, Okt 23, 2018 at 08:16:51 -0400, Hendrik Boom wrote:
On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
Make that: "there *was* a command, chkconfig:"
It's no longer present in Debian stable (stretch) and later. You can
still find it in oldstable (jessie) though. See
On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
> Hi,
>
> Bruce Ferrell writes:
>
> > [...]
> >
> > If I understand the original question "how to I get sysV init to not
> > start a process present in the init system", There is a command,
> > chkconfig:
>
> Make that: "there
Hi,
Bruce Ferrell writes:
> [...]
>
> If I understand the original question "how to I get sysV init to not
> start a process present in the init system", There is a command,
> chkconfig:
Make that: "there *was* a command, chkconfig:"
It's no longer present in Debian stable (stretch) and later.
On 10/21/18, Alessandro Selli wrote:
> I don't think init scripts are considered configuration files, as in
> fact the are not.
...
> So, I expect an update to overwrite the init script with the update's
> version regardless, and to reset the permissions to those set in the
> package.
All
On Mon, 22 Oct 2018 20:09:55 +0100, Simon wrote in message
<5f3ba84f-752c-4bee-b0c6-8e31b10f3...@thehobsons.co.uk>:
> Arnt Karlsen wrote:
>
> > ..well, that's still 256 possible runlevel names. ;o)
>
> TBH, I don't think there's all that much scope for **usefully** using
> lots of
On 10/22/18 6:14 AM, KatolaZ wrote:
On Mon, Oct 22, 2018 at 02:54:40PM +0200, Arnt Karlsen wrote:
[cut]
sysvinit currently supports runlevels 0-6, with 0 and 6 have special,
fixed meaning. There is *currently* no way of naming a runlevel using
more than one character, due to the way the
Arnt Karlsen wrote:
> ..well, that's still 256 possible runlevel names. ;o)
TBH, I don't think there's all that much scope for **usefully** using lots of
runlevels.
To start with, (near enough) every package comes with a control script for rc
to use - and which contains comments to signal to
On Mon, 22 Oct 2018 15:14:48 +0200, KatolaZ wrote in message
<20181022131448.c77g4mldzlcjv...@katolaz.homeunix.net>:
> On Mon, Oct 22, 2018 at 02:54:40PM +0200, Arnt Karlsen wrote:
>
> [cut]
>
> > > sysvinit currently supports runlevels 0-6, with 0 and 6 have
> > > special, fixed meaning.
On Mon, Oct 22, 2018 at 02:54:40PM +0200, Arnt Karlsen wrote:
[cut]
> > sysvinit currently supports runlevels 0-6, with 0 and 6 have special,
> > fixed meaning. There is *currently* no way of naming a runlevel using
> > more than one character, due to the way the "change runlevel"
> >
On Mon, 22 Oct 2018 12:40:20 +0200, KatolaZ wrote in message
<20181022104020.acw7kg5hbcnfd...@katolaz.homeunix.net>:
> On Sun, Oct 21, 2018 at 11:18:39PM +0200, Arnt Karlsen wrote:
> > On Sun, 21 Oct 2018 19:07:36 +0200, Didier wrote in message
> >
On Sun, Oct 21, 2018 at 11:18:39PM +0200, Arnt Karlsen wrote:
> On Sun, 21 Oct 2018 19:07:36 +0200, Didier wrote in message
> <826ba68a-6289-d047-7e74-d970996d2...@in2p3.fr>:
>
> > Le 21/10/2018 à 19:01, Didier Kryn a écrit :
> > > I'm not an expert, but it seems to me the answer is in
Le 21/10/2018 à 23:18, Arnt Karlsen a écrit :
On Sun, 21 Oct 2018 19:07:36 +0200, Didier wrote in message
<826ba68a-6289-d047-7e74-d970996d2...@in2p3.fr>:
Le 21/10/2018 à 19:01, Didier Kryn a écrit :
I'm not an expert, but it seems to me the answer is in inittab;
the following line
On Sun, 21 Oct 2018 19:07:36 +0200, Didier wrote in message
<826ba68a-6289-d047-7e74-d970996d2...@in2p3.fr>:
> Le 21/10/2018 à 19:01, Didier Kryn a écrit :
> > I'm not an expert, but it seems to me the answer is in inittab;
> > the following line invokes the daemon which launches all the
>
On 21/10/18 at 15:32, Joel Roth wrote:
> On Sun, Oct 21, 2018 at 08:50:40AM -0400, Steve Litt wrote:
>> On Sun, 21 Oct 2018 02:25:04 -1000
>> Joel Roth wrote:
>>
>> I don't remember the symlink maintenance scripts, so I
>> usually do this:
>>
>> chmod a-x /etc/init.d/exim4
>> Does your next
Le 21/10/2018 à 19:01, Didier Kryn a écrit :
I'm not an expert, but it seems to me the answer is in inittab;
the following line invokes the daemon which launches all the scripts:
si::sysinit:/etc/init.d/rcS
Well, there is also the following lines:
l0:0:wait:/etc/init.d/rc 0
On Sun, Oct 21, 2018 at 08:50:40AM -0400, Steve Litt wrote:
> On Sun, 21 Oct 2018 02:25:04 -1000
> Joel Roth wrote:
>
> > On Sat, Oct 20, 2018 at 11:52:53PM -0700, Jimmy Johnson wrote:
> > > On 10/20/18 11:18 PM, J. Fahrner wrote:
> > > > Am 2018-10-21 08:10, schrieb Steve Litt:
> > > > > In
On 21.10.18 08:18, J. Fahrner wrote:
> Am 2018-10-21 08:10, schrieb Steve Litt:
> > In Devuan, what's the command to permanently prevent sysvinit from
> > starting a daemon.
>
> man update-rc.d
>
> You can remove or disable a service.
And e.g. "view /etc/rc2.d/README" recites chapter and verse,
On Sun, 21 Oct 2018 02:25:04 -1000
Joel Roth wrote:
> On Sat, Oct 20, 2018 at 11:52:53PM -0700, Jimmy Johnson wrote:
> > On 10/20/18 11:18 PM, J. Fahrner wrote:
> > > Am 2018-10-21 08:10, schrieb Steve Litt:
> > > > In Devuan, what's the command to permanently prevent sysvinit
> > > > from
On Sat, Oct 20, 2018 at 11:52:53PM -0700, Jimmy Johnson wrote:
> On 10/20/18 11:18 PM, J. Fahrner wrote:
> > Am 2018-10-21 08:10, schrieb Steve Litt:
> > > In Devuan, what's the command to permanently prevent sysvinit from
> > > starting a daemon.
> >
> > man update-rc.d
> >
> > You can remove
On 10/20/18 11:18 PM, J. Fahrner wrote:
Am 2018-10-21 08:10, schrieb Steve Litt:
In Devuan, what's the command to permanently prevent sysvinit from
starting a daemon.
man update-rc.d
You can remove or disable a service.
Jochen
Can a person simple remove the 'exe' properties from the rc-*
Am 2018-10-21 08:10, schrieb Steve Litt:
In Devuan, what's the command to permanently prevent sysvinit from
starting a daemon.
man update-rc.d
You can remove or disable a service.
Jochen
___
Dng mailing list
Dng@lists.dyne.org
Hi all,
In Devuan, what's the command to permanently prevent sysvinit from
starting a daemon.
Yeah, I know I could research this, but I don't need to become a
sysvinit expert when so many such experts reside here.
Thanks,
SteveT
Steve Litt
September 2018 featured book: Quit Joblessness:
33 matches
Mail list logo
