using watershed in apport-noui.service causes multiple instances of watershed to run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I've modified /lib/systemd/
ExecStart=
With the hope that bug 1473562 will be resolved under systemd. (Note that using watershed works with upstart and /etc/init/
I've tested this by setting the PathExistsGlob to '/var/crash/
journalctl --since "4 min ago" /lib/udev/watershed
-- Logs begin at Sat 2015-06-27 08:38:54 PDT, end at Tue 2015-07-21 15:10:21 PDT. --
Jul 21 15:10:07 impulse watershed[22068]: Collecting info for /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: Marking /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: /var/crash/
Jul 21 15:10:07 impulse watershed[22068]: All reports processed
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: /var/crash/
Jul 21 15:10:08 impulse watershed[22308]: All reports processed
....
So watershed is called a number of times equal to the number of .crash files that exist in /var/crash/.
I'm looking for a way to limit the number of instances of whoopsie-upload-all run on boot up in systemd and I'm not certain if this behavior is a bug or if I haven't found the right way to set this limit.