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.

Description of problem:

When logging command output, script fails if the underlying write system call fails with EINTR.

This is peripherally related to this glibc upstream bug:

  https://sourceware.org/bugzilla/show_bug.cgi?id=21004

But as noted in this bug, I'm not convinced we should change the behavior within glibc.

This should be fixed by switching to a direct write system call with an EINTR retry loop, or installing the signal handler with SA_RESTART.

Version-Release number of selected component (if applicable):

util-linux-2.23.2-33.el7.x86_64

How reproducible:

Rarely.

Steps to Reproduce:
1. Run script to capture output from a long-running process under screen.
2. Detach the screen and reattach it with a different terminal size.

Actual results:

script exits with: “script: write failed: Interrupted system call”.  Any pending data is discarded.

Expected results:

script continues to run.

That's right, the current upstream uses write_all()
https://github.com/karelzak/util-linux/blob/master/include/all-io.h. These issue should be already fixed on Fedora.

Do you think the problem is important enough to backport the change to RHEL7? (I'm not sure:-)

(In reply to Karel Zak from comment #1)
> That's right, the current upstream uses write_all()
> https://github.com/karelzak/util-linux/blob/master/include/all-io.h. These
> issue should be already fixed on Fedora.
> 
> Do you think the problem is important enough to backport the change to
> RHEL7? (I'm not sure:-)

Is there any other tool which can be used to capture output from a terminal?  Maybe I could use screen itself or tmux.

I need this for glibc testing, to capture full crash output (including backtraces).  If there is no other option, I would appreciate a fixed script program.

I don't want to force you to use something else, just asking how important it is.

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://access.redhat.com/errata/RHBA-2018:0936