Your message dated Sun, 23 Jul 2017 15:57:32 +0200
with message-id <[email protected]>
and subject line Re: Bug#869422: systemd-logind lacks an init script
has caused the Debian Bug report #869422,
regarding systemd-logind lacks an init script
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.)


-- 
869422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869422
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 232-25+deb9u1
Severity: normal

I upgraded my Jessie installation to Stretch recently following the description 
in the Stretch release notes. I use sysvinit instead of systemd. Since the 
upgrade I see a process called systemd-logind that doesn't seem to have in init 
script so it cannot be restarted when there are library updates. Please provide 
an init script. Also, when I first login as a user it produces the message 
"systemd-logind[3215]: Failed to start user service, ignoring: Unknown unit: 
[email protected]" on the console.

-- Package-specific info:

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages systemd depends on:
ii  adduser         3.115
ii  libacl1         2.2.52-3+b1
ii  libapparmor1    2.11.0-3
ii  libaudit1       1:2.6.7-2
ii  libblkid1       2.29.2-1
ii  libc6           2.24-11+deb9u1
ii  libcap2         1:2.25-1
ii  libcryptsetup4  2:1.7.3-4
ii  libgcrypt20     1.7.6-2+deb9u1
ii  libgpg-error0   1.26-2
ii  libidn11        1.33-1
ii  libip4tc0       1.6.0+snapshot20161117-6
ii  libkmod2        23-2
ii  liblz4-1        0.0~r131-2+b1
ii  liblzma5        5.2.2-1.2+b1
ii  libmount1       2.29.2-1
ii  libpam0g        1.1.8-3.6
ii  libseccomp2     2.3.1-2.1
ii  libselinux1     2.6-3+b1
ii  libsystemd0     232-25+deb9u1
ii  mount           2.29.2-1
ii  procps          2:3.3.12-3
ii  util-linux      2.29.2-1

Versions of packages systemd recommends:
ii  dbus            1.10.18-1
ii  libpam-systemd  232-25+deb9u1

Versions of packages systemd suggests:
ii  policykit-1        0.105-18
pn  systemd-container  <none>
pn  systemd-ui         <none>

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.130
ii  udev             232-25+deb9u1

--- End Message ---
--- Begin Message ---
Am 23.07.2017 um 14:21 schrieb [email protected]:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: normal
> 
> I upgraded my Jessie installation to Stretch recently following the 
> description in the Stretch release notes. I use sysvinit instead of systemd. 
> Since the upgrade I see a process called systemd-logind that doesn't seem to 
> have in init script so it cannot be restarted when there are library updates. 
> Please provide an init script. Also, when I first login as a user it produces 
> the message "systemd-logind[3215]: Failed to start user service, ignoring: 
> Unknown unit: [email protected]" on the console.

logind is a D-Bus activated service. If you want to restart it, simply
killing the process should be sufficient. Thus there is no plan to add a
SysV init script.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to