On Fri, Sep 25, 2020 at 03:42:00PM -0000, Nicolas Bock wrote: > @balint I was wondering why we don't use `PathChanged` in the systemd > path file. This checks for any changes in the path and will pick up new > crash files... But after reading the systemd docs again I guess the > reason is that we want the service to activate if the crash directory > already contains a crash file on startup. Am I understanding this > correctly?
The issue with PathChanged is that /var/crash is used for writing three types of files. The .crash file, the .upload file (which signifies the crash is ready to be uploaded), and the .uploaded file (which contains the UUID of the crash in the error tracker and indicates the crash has been uploaded). So if PathChanged is used then whoopsie-upload-all will be called for .upload and .uploaded files. Additionally, there is no PathChangedGlob so that we could watch for just .crash files. To help with the issue I'm working on a change to whoopsie-upload-all to remove the .crash file after a .uploaded file exists. -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs