On Sun, 23.03.14 21:46, Patrick Donnelly (batr...@batbytes.com) wrote:
My problem is not related to race conditions. The issue is that
/proc/pid/cmdline is shown instead of /proc/pid/comm for each journal
entry. That is:
$ journalctl --boot
[...]
Mar 23 21:39:01 host a.out[10697]: hi
Mar
On Mon, Mar 24, 2014 at 12:30 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Sun, 23.03.14 21:46, Patrick Donnelly (batr...@batbytes.com) wrote:
My problem is not related to race conditions. The issue is that
/proc/pid/cmdline is shown instead of /proc/pid/comm for each journal
On Mon, 24.03.14 19:01, Patrick Donnelly (batr...@batbytes.com) wrote:
On Mon, Mar 24, 2014 at 12:30 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Sun, 23.03.14 21:46, Patrick Donnelly (batr...@batbytes.com) wrote:
My problem is not related to race conditions. The issue is
On Sun, 23.03.14 00:32, Patrick Donnelly (batr...@batbytes.com) wrote:
It seems the journal is reading from /proc/pid/cmdline (argv[0]) for
each entry. So when reading using journalctl, we don't see process
title changes properly. See the below example:
We are reading both /proc/$PID/comm and
[adding message to list, sorry Lennart...]
On Sun, Mar 23, 2014 at 9:25 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Sun, 23.03.14 00:32, Patrick Donnelly (batr...@batbytes.com) wrote:
It seems the journal is reading from /proc/pid/cmdline (argv[0]) for
each entry. So when reading
