Bug 55320 - journal: no _SYSTEMD_UNIT field for _TRANSPORT=stdout messages
Summary: journal: no _SYSTEMD_UNIT field for _TRANSPORT=stdout messages
Status: RESOLVED WORKSFORME
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-25 14:38 UTC by Oleksii Shevchuk
Modified: 2013-03-14 04:07 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Oleksii Shevchuk 2012-09-25 14:38:07 UTC
Journal should mark log records with _SYSTEMD_UNIT, if process assigned to unit or started in unit cgroup

// systemd latest
Comment 1 Zbigniew Jedrzejewski-Szmek 2013-03-14 04:07:49 UTC
Works for me:

$ journalctl _TRANSPORT=stdout -o verbose|grep -E 'MESSAGE|_TRANSPORT|_UNIT'
...
	_TRANSPORT=stdout
	_SYSTEMD_UNIT=dbus.service
	MESSAGE=Failed to issue method call: Unit winbind.service is not loaded.
	_TRANSPORT=stdout
	_SYSTEMD_UNIT=bluetooth.service
	MESSAGE=bluetoothd[765]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.