Your message dated Fri, 26 Oct 2018 10:40:59 +0800 with message-id <[email protected]> and subject line Re: [Pkg-sysvinit-devel] Bug#860152: Case of two inits has caused the Debian Bug report #860152, regarding sysvinit-core: after upgrading libc6, running init U in single user mode leaves extra init 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.) -- 860152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860152 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: sysvinit-core Version: 2.88dsf-59.9 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading libc6, going to single user mode, 2 init processes were left. Running: init U left the init process with pid > 1 still dependent on old libc6 * What exactly did you do (or not do) that was effective (or ineffective)? kill -9 of the init process with pid > 1 returned to multi-user mode with the init process of pid > 1 gone. * What was the outcome of this action? * What outcome did you expect instead? init U should restart all running init processes. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-rc6 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages sysvinit-core depends on: ii debconf [debconf-2.0] 1.5.60 ii debianutils 4.8.1.1 ii initscripts 2.88dsf-59.9 ii libc6 2.24-10 ii libselinux1 2.6-3+b1 ii libsepol1 2.6-2 ii sysv-rc 2.88dsf-59.9 ii sysvinit-utils 2.88dsf-59.9 sysvinit-core recommends no packages. Versions of packages sysvinit-core suggests: ii bootlogd 2.88dsf-59.9 -- debconf information: sysvinit/hurd-fix-inittab:
--- End Message ---
--- Begin Message ---Control: notfound -1 2.88dsf-59.9 Control: tags -1 wontfix Hi Jesse, Cc Arthur, Jesse Smith <[email protected]> writes: > If I'm understanding the situation here when the user dropped into > single-user mode there were two instances of init running? As far as I can see, by "init process", Arthur meant /etc/init.d/ daemons. > [...] @Arthur, from init(8), > U or u tell init to re-execute itself (preserving the state). No > re-examining of /etc/inittab file happens. Run level should be one of > Ss0123456 otherwise request would be silently ignored. init u only re-execute /sbin/init the binary, it has no relation with services in /etc/init.d. For that purpose, upgrading libc will trigger necessary service restarts automatically. Yours, Benda
--- End Message ---
