Bug 164548
| Summary: | man page does not specify if we build xterm with logging enabled or not | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Kevin Krafthefer <krafthef> |
| Component: | xterm | Assignee: | Jason Vas Dias <jvdias> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | dickey, tao |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | RHEL4U3NAK | ||
| Fixed In Version: | RHBA-2006-0350 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-05-10 22:12:03 UTC | Type: | --- |
| 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: | 187538 | ||
The menu entry is only present if the code supports it. (Perhaps sometime I should generate flavors of the manpage based on xtermcfg.h). This bug is now fixed with xterm-192-2.EL4 . As this is ON_QA moving to RHEL4U4Proposed, clearing ACKs. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0350.html |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1 Description of problem: The manpage for xterm on RHEL states this: -l Turn logging on. Normally logging is not supported, due to security concerns. Some versions of xterm may have logging enabled. The logfile is written to the directory from which xterm is invoked. The filename is generated, of the form XtermLog.XXXXXX or Xterm.log.hostname.yyyy.mm.dd.hh.mm.ss.XXXXXX depending on how xterm was built. We need to specify how we build it for RHEL. Version-Release number of selected component (if applicable): xterm-192-1 How reproducible: Always Steps to Reproduce: 1. man xterm 2. 3. Actual Results: get ambiguous documentation. Expected Results: get definitive documentation. Additional info: