Comment 2 for bug 2060310
Revision history for this message
| Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
If setting "NotifyAccess=all" and with systemd debug traces enabled, it is possible to see the notifications sent from these processes to systemd in the journal:
Apr 05 17:14:57 qemuname systemd[1]: snapd.service: Got notification message from PID 5112 (EXIT_STATUS=0)
Apr 05 17:14:57 qemuname systemd[1]: snapd.service: Got notification message from PID 5113 (EXIT_STATUS=0)
Apr 05 17:14:57 qemuname systemd[1]: snapd.service: Got notification message from PID 5147 (EXIT_STATUS=0)
Apr 05 17:14:58 qemuname systemd[1]: snapd.service: Got notification message from PID 5149 (EXIT_STATUS=0)
Processes being:
pid: 5112, ppid: 5106, comm: snapd, args: systemctl --version
pid: 5113, ppid: 5106, comm: snapd, args: systemd-detect-virt
pid: 5147, ppid: 5108, comm: snapd, args: systemctl is-enabled snapd.apparmor
pid: 5149, ppid: 5114, comm: snapd, args: udevadm info -e
These EXIT_STATUS notifications have been introduced recently in systemd and seem to be informational for services at the moment [1].
[1] https:/