Bug 1268336
| Summary: | systemd-analyze set-log-level manpage fix | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Zdenek Pytela <zpytela> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | fsumsal, jscotka, lnykryn, systemd-maint-list |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-219-20.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 00:44:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1203710, 1289485, 1313485 | ||
|
Description
Zdenek Pytela
2015-10-02 14:39:27 UTC
The coredump is fixed in 7.2. I will submit a patch to upstream regarding the manpage. Thanks for the fix. There is no need to accelerate to RHEL 7.1 at the moment. However, there are two outstanding questions: 1. Is it possible to determine the current log level? I was not able to find it in any manual page or other resources. 2. According to the systemd(1) manual page, log-level subcommand should accept either a numerical log level or syslog symbolic names. If an incorrect argument is passed, rather cryptic message is displayed: # systemd-analyze set-log-level 42 Failed to issue method call: Access denied Can we also consider this to be a bug? > 1. Is it possible to determine the current log level? I was not able to find > it in any manual page or other resources. I am not sure if there is a nice interface for it. It is visible on dbus. [lnykryn@notas lnykryn-systemd]$ busctl get-property org.freedesktop.systemd1 /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager LogLevel s "info" > 2. According to the systemd(1) manual page, log-level subcommand should > accept either a numerical log level or syslog symbolic names. If an > incorrect argument is passed, rather cryptic message is displayed: > > # systemd-analyze set-log-level 42 > Failed to issue method call: Access denied > > Can we also consider this to be a bug? There is already a bug that error messages are cryptic. We need to fix it somehow. pushed to staging -> https://github.com/lnykryn/systemd-rhel/commit/ffe00d391c0cfc52897820bb19c6a0b8a43680d8 -> post Verified with systemd-219-27.el7. Old version: # man systemd-analyze <...> systemd-analyze [OPTIONS...] set-log-level [LEVEL] <...> # systemd-analyze set-log-level This command expects one argument only. *** Error in `systemd-analyze': free(): invalid size: 0x00007fff3a983340 *** <...> Aborted # echo $? 134 New version: # man systemd-analyze <...> systemd-analyze [OPTIONS...] set-log-level LEVEL <...> # systemd-analyze set-log-level This command expects one argument only. # echo $? 1 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2216.html |