Bug#857159: Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd

Michael Biebl biebl at debian.org
Wed Mar 8 19:32:04 GMT 2017


Am 08.03.2017 um 20:12 schrieb Alexandre Detiste:
> Hi,
> 
>> systemd-cron *does* stop cron.target in prerm in recent versions, but
>> stopping cron.target *does not* stop cron-update.path.
>>
>> Contrary to the other units, cron-update.path is not marked as
>> PartOf=cron.target.
> 
> So could it be enough to just add this "PartOf=cron.target"
> to  cron-update.path too ?

I think so, yes. Unless upstream had a specific reason not to do it this
way. I notice that for the other units it also uses Requires, but Wants
for cron-update.path

>> And due to the use of
>> RefuseManualStart=yes
>> RefuseManualStop=yes
> 
> This has been cargo culted & could also be changed,
> but I prefer the first option (the .target that controls everything).

I don't see a good reason why the individual units should not be
stoppable/startable by the admin, so I'd probably drop it for all the
units. Again, ask upstream. Maybe there is a good reason for this.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170308/57cd013b/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list