Bug#930120: init: Documentation error for telinit/init - does not use 'systemctl isolate xxx'
On Fri, 7 Jun 2019 17:32:00 +0200 Michael Biebl 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 I still don't see the problem here, that said if you feel strongly about this and think this needs to be addressed, please raise this upstream at https://github.com/systemd/systemd/issues After all, this doesn't look like a Debian specific issue. Regards, 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
Bug#930120: init: Documentation error for telinit/init - does not use 'systemctl isolate xxx'
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 -- 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
Bug#930120: init: Documentation error for telinit/init - does not use 'systemctl isolate xxx'
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
