Bug 1253055
| Summary: | Xorg log does not exist in RHEL 7.2 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Swapna Krishnan <skrishna> |
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | jeff.burrell, mdomonko, tpelka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gdm-3.14.2-12.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 07:16:37 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: | 1190227 | ||
|
Description
Swapna Krishnan
2015-08-12 20:36:32 UTC
My guess it is because root 1798 0.0 0.8 431784 104684 tty1 Ssl+ Aug11 2:12 /usr/bin/Xorg :0 -background none -noreset -audit 4 -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-oTTj9L/database -seat seat0 -nolisten tcp vt1 Is it expected Xorg is running with "-logfile /dev/null" it was an intentional upstream change to move X logging to the journal. The journal gets mirrored to /var/log/messages by rsyslog in RHEL7 (but we don't use rsyslog in recent versions of fedora). Whether or not we should keep 7.2 like this, I'm not completely sure. Customers might get thrown off by the logs moving. Also in RHEL 6, customers complained when certain GDM logs ended up in syslog ( see bug 834303 ) So I'm thinking we should probably change the logs back to the same locations as 7.1 to be conservative and customer friendly. *** Bug 1255913 has been marked as a duplicate of this bug. *** 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-2015-2216.html |