Your message dated Mon, 2 Dec 2019 18:14:52 +0100
with message-id <[email protected]>
and subject line Re: Bug#930120: init: Documentation error for telinit/init -
does not use 'systemctl isolate xxx'
has caused the Debian Bug report #930120,
regarding init: Documentation error for telinit/init - does not use 'systemctl
isolate xxx'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
930120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930120
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: init
Version: 1.56+nmu1
Severity: minor
Tags: upstream
Dear Maintainer,
The man page of telinit/init says (for 'telinit N'):
Change the SysV runlevel. This is translated into an activation request for
runlevel2.target,
runlevel3.target, ... and is equivalent to systemctl isolate
runlevel2.target, systemctl isolate
runlevel3.target, ...
But when using telinit 2 or init 2 (or event booting the kernel with "2"
as an argument), the effective operation is:
'systemctl start runlevel2.target'
### but not 'sytemctl isolate runlevel2.target' ### as documented
I also suspect that booting with "2" as a kernel commandline argument
starts "multi-user.target" instead of "runlevel2.target". At least for
me things work as expected when using systemd.unit=runlevel2.target at
boot time, or 'systemctl isolate runlevel2.target' after boot.
Systemdaemon is nice and works fine otherwise.
Thanks, Jürgen
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages init depends on:
ii init-system-helpers 1.56+nmu1
ii systemd-sysv 241-5
init recommends no packages.
init suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 19 Jun 2019 22:06:11 +0200 Michael Biebl <[email protected]> wrote:
> On Fri, 7 Jun 2019 17:32:00 +0200 Michael Biebl <[email protected]> wrote:
> > Control: tags -1 + moreinfo
> >
> > Am 07.06.19 um 15:51 schrieb J. Pfennig:
> > > The man page of telinit/init says (for 'telinit N'):
> > >
> > > Change the SysV runlevel. This is translated into an activation
> > > request for runlevel2.target,
> > > runlevel3.target, ... and is equivalent to systemctl isolate
> > > runlevel2.target, systemctl isolate
> > > runlevel3.target, ...
> > >
> > > But when using telinit 2 or init 2 (or event booting the kernel with "2"
> > > as an argument), the effective operation is:
> > >
> > > 'systemctl start runlevel2.target'
> > > ### but not 'sytemctl isolate runlevel2.target' ### as documented
> > >
> >
> > I'm pretty sure "telinit" uses isolate.
> > See
> > https://github.com/systemd/systemd/blob/master/src/initctl/initctl.c#L101
> >
> > So the documentation looks correct to me.
> > Please elaborate
>
Ok, let's close this bug report. According to the sources, initctl does
seem to use isolate, so the documentation appears correct.
I don't see anything in the bug report which would indicate that telinit
does not behave as documented.
If I missed that, please point out the difference in behavious
specifically, and we can reopen the bug report.
Thanks,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
