Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Document URL:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/recording_sessions/index
Suggestions for improvement:
Add note about expected behavior of terminal output flooding when tailing logs inside a tlog recorded terminal session(tail -f /var/log/messages or journalctl -f).
When tlog recording is configured to log to the journal/syslog, the recorded user is seeing the act of recording the results of viewing the system journal or /var/log/messages. Since viewing generates logs, which then print to the screen, this causes session recording to record this action, which generates more records, causing a loop of flooded output.
The following command can be used as an alternative to the typical 'journalctl -f' command run inside a recorded session
# journalctl -f | grep -v 'tlog-rec-session'
Tlog can also be configured to rate limit(throttle) output, refer to man tlog-rec or man tlog-rec-session for more detail.
This can be added to the section:
---------------------------
1.3. Limitations of session recording
Be aware that tlog does not record terminal in the Gnome 3 graphical session. Recording terminals in graphical sessions is not supported because a graphical session has a single audit session ID for all terminals and tlog does not have a way to distinguish between the terminals and prevent repeated recordings.