Le lundi 8 février 2016, 18:18:20 Yuriy M. Kaminskiy a écrit :
> Problem is, we started executing unit, spawned StartPre command, then
> unit file was removed, systemctl daemon-reload was issued, unit
> structure become half-ghost, then we got SIGCHLD for that StartPre
> command from the
Le lundi 8 février 2016, 02:36:07 Michael Biebl a écrit :
> Am 06.02.2016 um 10:56 schrieb Sebastien Koechlin:
>
> > Removing systemd-cron, installing cron
> >
> > Feb 05 20:51:03 debir systemd[1]: Starting systemd-cron update units...
> > Feb 05 20:51:03 debir systemd[1]: Reloading.
> > Feb 05
Michael,
> Alexandre, do you think backporting check changes for #776859 are feasible?
I created a "jessie" with the one-line fix; can I help more ?
http://anonscm.debian.org/cgit/collab-maint/systemd-cron.git/log/?h=jessie
signature.asc
Description: This is a digitally signed message part.
Processing commands for cont...@bugs.debian.org:
> tags 546532 + pending
Bug #546532 [init-system-helpers] invoke-rc.d: does not default to a sensitive
behaviour when no start o stop symlink is found
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need
On 08.02.2016 02:15, Yuriy M. Kaminskiy wrote:
Package: systemd
Version: 215-17+deb8u3
Severity: important
Probably related:
cron-update.service is triggered by some /etc/cron* directories change
and invokes `systemctl daemon-reload` and `systemctl try-restart
cron.target`. Maybe there are
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #775651 (http://bugs.debian.org/775651)
# Bug title: systemd: /run/user/$UID
#
# bts-link upstream status pull for source package src:systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #769187 (http://bugs.debian.org/769187)
# Bug title: general: Entries in system