Your message dated Tue, 1 Aug 2017 16:22:46 +0200
with message-id <[email protected]>
and subject line Re: Bug#870350: systemd: "systemctl disable --now" doesn't 
stop either cron or fetchmail
has caused the Debian Bug report #870350,
regarding systemd: "systemctl disable --now" doesn't stop either cron or 
fetchmail
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.)


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

Dear Maintainer,

According to the documentation,

    systemctl disable service --now

stops the service. For example, `man systemctl` says:

  --now
      When used with enable, the units will also be started. When used
      with disable or mask, the units will also be stopped. The start
      or stop operation is only carried out when the respective enable
      or disable operation has been successful.

But here it doesn't, at least for cron and fetchmail.

See output below.

This is similar to https://bugs.debian.org/804438 and may be related
or a dupe.

Regards, Faheem Mitha

root@orwell:/home/faheem# systemctl disable cron --now
Synchronizing state of cron.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable cron
insserv: warning: current start runlevel(s) (empty) of script `cron' overrides 
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (2 3 4 5) of script `cron' overrides 
LSB defaults (empty).

root@orwell:/home/faheem# systemctl status cron
● cron.service - Regular background program processing daemon
   Loaded: loaded (/lib/systemd/system/cron.service; disabled; vendor preset: 
enabled)
   Active: active (running) since Mon 2017-07-31 12:25:36 IST; 1 day 3h ago
     Docs: man:cron(8)
 Main PID: 10356 (cron)
      CPU: 3ms
   CGroup: /system.slice/cron.service
           ├─10356 /usr/sbin/cron -f
           ├─23104 /usr/sbin/CRON -f
           ├─23105 /usr/sbin/CRON -f
[...]

###################################################################################################
root@orwell:/home/faheem# systemctl disable fetchmail --now
fetchmail.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable fetchmail
insserv: warning: current stop runlevel(s) (empty) of script `fetchmail' 
overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `fetchmail' 
overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (2 3 4 5) of script `fetchmail' 
overrides LSB defaults (0 1 6).

root@orwell:/home/faheem# systemctl status fetchmail
● fetchmail.service - LSB: init-Script for system wide fetchmail daemon
   Loaded: loaded (/etc/init.d/fetchmail; generated; vendor preset: enabled)
   Active: active (running) since Mon 2017-07-31 12:23:20 IST; 1 day 3h ago
     Docs: man:systemd-sysv-generator(8)
      CPU: 18ms
   CGroup: /system.slice/fetchmail.service
           └─9777 /usr/bin/fetchmail -f /etc/fetchmailrc --pidfile 
/var/run/fetchmail/fetchmail.pid -d 300 --syslog
[...]

-- Package-specific info:

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

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

-- debconf-show failed

--- End Message ---
--- Begin Message ---
Version: 234-1

Am 01.08.2017 um 12:50 schrieb Faheem Mitha:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: normal
> 
> Dear Maintainer,
> 
> According to the documentation,
> 
>     systemctl disable service --now
> 
> stops the service. For example, `man systemctl` says:
> 
>   --now
>       When used with enable, the units will also be started. When used
>       with disable or mask, the units will also be stopped. The start
>       or stop operation is only carried out when the respective enable
>       or disable operation has been successful.
> 
> But here it doesn't, at least for cron and fetchmail.
> 

Seems to be fixed in unstable, i.e. for v234, so marking the bug
accordingly.

Regards,
Michael


-- 
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