On Di, 28.07.20 12:12, Ian Pilcher (arequip...@gmail.com) wrote:
> On 7/28/20 9:44 AM, Lennart Poettering wrote:
> > Is the service short-lived? There's a race: if a process runs very
> > quickly and logs journald might process the message after the process
> > already exited, i.e. at a time where
On 7/28/20 9:44 AM, Lennart Poettering wrote:
Is the service short-lived? There's a race: if a process runs very
quickly and logs journald might process the message after the process
already exited, i.e. at a time where we can't read the cgroup off the
process anymore.
It is indeed a very short
On Sa, 25.07.20 17:22, Ian Pilcher (arequip...@gmail.com) wrote:
> I have a simple (non-forking) one-shot service that logs messages via
> syslog. These messages are not being "associated" with the service
> unit. I.e., they don't show up if I use journalctl's -u option
> (although they are in t
I have a simple (non-forking) one-shot service that logs messages via
syslog. These messages are not being "associated" with the service
unit. I.e., they don't show up if I use journalctl's -u option
(although they are in the journal).
UPDATE: I just tried using sd_journal_print, and I'm seein
