Your message dated Thu, 15 Dec 2016 21:23:08 +0100
with message-id <[email protected]>
and subject line Re: Bug#790262: systemd: warns that service changes on disk 
instead of just reloading
has caused the Debian Bug report #790262,
regarding systemd: automatically reload unit files when changed on disk
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.)


-- 
790262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790262
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 220-7
Severity: normal

If I edit a file on disk, and then attempt to use service to restart it,
systemd warns but does not reload the file:

  castro ok % sudo service krb5-kdc restart
  Warning: krb5-kdc.service changed on disk. Run 'systemctl daemon-reload' to 
reload units.
  ^C%

When I invoked service, I expected systemd to just reload the unit
instead of warning me that it had changed.  After all, I wouldn't have
edited the file unless I wanted systemd to do something different with
the service.  systemd should just reload the file (or files)
automatically, since that's what the user expects to happen; the
behavior is also consistent with sysvinit.

-- Package-specific info:

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

Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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.113+nmu3
ii  libacl1         2.2.52-2
ii  libapparmor1    2.9.2-3
ii  libaudit1       1:2.4.2-1
ii  libblkid1       2.26.2-6
ii  libc6           2.19-18
ii  libcap2         1:2.24-9
ii  libcap2-bin     1:2.24-9
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.3-2
ii  libkmod2        20-1
ii  liblzma5        5.1.1alpha+20120614-2+b3
ii  libmount1       2.26.2-6
ii  libpam0g        1.1.8-3.1
ii  libseccomp2     2.2.1-2
ii  libselinux1     2.3-2+b1
ii  libsystemd0     220-7
ii  mount           2.26.2-6
ii  sysv-rc         2.88dsf-59.2
ii  udev            220-7
ii  util-linux      2.26.2-6

Versions of packages systemd recommends:
ii  dbus            1.8.18-1
ii  libpam-systemd  220-7

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- Configuration Files:
/etc/systemd/system.conf changed [not included]

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
On Sat, 27 Jun 2015 16:56:03 -0300 Felipe Sateler <[email protected]>
wrote:
> Control: tags -1 wontfix
> Control: severity -1 wishlist
> 
> 
> On 27 June 2015 at 16:15, brian m. carlson <[email protected]> 
> wrote:
> > Package: systemd
> > Version: 220-7
> > Severity: normal
> >
> > If I edit a file on disk, and then attempt to use service to restart it,
> > systemd warns but does not reload the file:
> >
> >   castro ok % sudo service krb5-kdc restart
> >   Warning: krb5-kdc.service changed on disk. Run 'systemctl daemon-reload' 
> > to reload units.
> >   ^C%
> >
> > When I invoked service, I expected systemd to just reload the unit
> > instead of warning me that it had changed.  After all, I wouldn't have
> > edited the file unless I wanted systemd to do something different with
> > the service.  systemd should just reload the file (or files)
> > automatically, since that's what the user expects to happen; the
> > behavior is also consistent with sysvinit.
> 
> Systemd upstream has been quite clear that they do not want
> autoreloads[1]. 

Closing this as wontfix, as it's clear that this is not going to change.


-- 
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 ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to