On 2018-03-17, Michael Grant <mgr...@grant.org> wrote: > --f403043615085592a505679a4cd2 > Content-Type: text/plain; charset="UTF-8" > > I restarted ntp today and noticed this in the logs: > > Mar 17 07:12:41 bottom systemd[1]: > /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue > 'SuccessAction' in section 'Service' > Mar 17 07:12:42 bottom systemd[1]: > /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue > 'SuccessAction' in section 'Service' > Mar 17 07:12:43 bottom systemd[1]: > /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue > 'SuccessAction' in section 'Service' > Mar 17 07:12:44 bottom systemd[1]: > /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue > 'SuccessAction' in section 'Service' > Mar 17 07:12:44 bottom systemd[1]: > /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue > 'SuccessAction' in section 'Service' > Mar 17 07:12:50 bottom systemd[1]: Stopping Network Time Service... > > So I looked at this line in the system-update-cleanup.service file: > > SuccessAction=reboot > > It's the last line in the file in the [Service] section. A little research > shows that this line seems to belong in the [Unit] section. > > Dare I move it? Not sure if this is a known bug or if this is just some > rot that's occurred over time on my debian systems. > > I don't really know what this file does with respect to stopping ntp but it > would be a bit odd if my system rebooted when I simply restarted ntp! >
The file /lib/systemd/system/system-update-cleanup.service is unknown to the package manager in stretch. What distro and version are you running?
