Thanks for your bug report. Indeed, it seems the check for systemd being used is not accurate and needs to be reviewed.
I'll look into this and try to fix it. Saludos, Javier El 09/05/2015 13:27, "Francesco Poli (wintermute)" < invernom...@paranoici.org> escribió: > Package: debian-goodies > Version: 0.64 > Severity: normal > > Hello Javier, > I noticed that, after the > [UPGRADE] debian-goodies:amd64 0.63 -> 0.64 > checkrestart suggests to restart some services by using "systemctl", > rather than by using "service". This may be the right strategy on > boxes that run systemd as PID 1, but it appears to be definitely > non-working on boxes which use another init system (such as sysvinit). > > For instance, it happened to me more than once (since the upgrade) > to get the following output from checkrestart: > > [...] > | Of these, 1 seem to contain systemd service definitions or init scripts > which can be used to restart them. > | The following packages seem to have definitions that could be used > | to restart their services: > | colord: > | 2252 /usr/lib/colord/colord > | > | These are the systemd services: > | systemctl restart colord.service > [...] > > But, on my box, I run sysvinit as PID 1, and hence, if I try to issue > the command, I get an error message and nothing else happens: > > # systemctl restart colord.service > Failed to get D-Bus connection: Unknown error -1 > > I see from the changelog that this is part of preliminary support > for systemd: > > [...] > | - Add preliminary support for systemd in checkrestart. Now, if the > | system is using systemd and there are service files for a package the > | admin is pointed to 'systemctl' (and systemd itself is ignored by > | checkrestart). Compatibility with packages only providing init.d > files > | (or not using systemd) is still maintained. > [...] > > I suppose that this is a first step to address bug #678366, > but it seems to me that the "if the system is using systemd" > condition is not checked properly. > > Please note that I have sysvinit-core and systemd-shim installed > on my box, and not systemd-sysv: > > $ aptitude search sysvinit systemd | tail -n 10 > i A systemd - system and service manager > p systemd-cron - systemd units to provide minimal > cron daem > p systemd-dbg - system and service manager (debug > symbols) > p systemd-gui - transitional package for systemd-ui > i systemd-shim - shim for systemd > p systemd-sysv - system and service manager - SysV > links > p systemd-ui - graphical frontend for systemd > i sysvinit - System-V-like init utilities - > transitiona > i A sysvinit-core - System-V-like init utilities > i sysvinit-utils - System-V-like utilities > > > Please fix the "is systemd running as PID 1?" check. > > Thanks for your time! > Bye. > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (800, 'testing'), (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > Init: sysvinit (via /sbin/init) > > Versions of packages debian-goodies depends on: > ii curl 7.42.1-2 > ii dctrl-tools [grep-dctrl] 2.23 > ii dialog 1.2-20140911-1 > ii perl 5.20.2-4 > ii python 2.7.9-1 > ii whiptail 0.52.17-1+b1 > > Versions of packages debian-goodies recommends: > ii lsof 4.86+dfsg-1 > > Versions of packages debian-goodies suggests: > ii popularity-contest 1.62 > ii xdg-utils 1.1.0~rc1+git20111210-7.4 > ii zenity 3.14.0-1 > > -- no debconf information >
