Bug 67054 - RFE - Add options to shorten or skip hostname on output
Summary: RFE - Add options to shorten or skip hostname on output
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All All
: medium enhancement
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-18 17:22 UTC by Orion Poplawski
Modified: 2013-08-13 21:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Orion Poplawski 2013-07-18 17:22:28 UTC
Since I think journalctl generally only handles messages for the local machine, is it even necessary to output the hostname, esp. the fully qualified hostname?

At the very least, options to be able to shorten or eliminate the output of hostname would be nice.
Comment 1 Lennart Poettering 2013-07-24 10:40:49 UTC
We show the kernel hostname, not the fqdn. If you initialize the kernel hostname to the fqdn it's kinda your own fault...

journalctl handles messages from as many hosts as you like. For example, if you share the journal dir from multiple hosts, you can use "journalctl -m" to merge the output of all of them. This is also used by "systemd-nspawn -j" to make the logs available easily. 

Also we try to stay compatible with classic /var/log/messages in our output, so that people can parse the lines with the classic tools.

All together I am really not convinced that it would be a good idea to not show the name.
Comment 2 Orion Poplawski 2013-08-13 21:11:34 UTC
(In reply to comment #1)
> We show the kernel hostname, not the fqdn. If you initialize the kernel
> hostname to the fqdn it's kinda your own fault...

Well, FWIW - IPA/kerberos appears to demand that the hostname be set to the fqdn:

Joining realm failed: The hostname must be fully-qualified: barry

So I still think this would be a useful option.


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.