Stephen Smalley wrote:
On Thu, 2006-12-07 at 18:15 -0500, Linda Knippers wrote:
I was having intermittent problems with the 'more' command and finally
had a chance to identify the problem.
The symptom is that 'more' will abort after one screen full, getting
an EBADF when it tries to read the user input. It doesn't matter if
the system is in permissive mode. The issue is that 'more' is reading
stderr. That's not a problem until one runs 'newrole', which is
paranoid about stdout and stderr, reopening them as WRONLY.
I filed a bugzilla on the problem.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218880
Do we change 'more'? I wonder what else will stop working with the
current 'newrole' behavior.
I think we revert newrole to its prior behavior (it used to open all
three descriptors rw, but that was "cleaned up").
So I'm not sure why more would be reading stderr, that doesn't make
sense at all to me. Assuming this is unreasonable, we shouldn't be
changing newrole, but fixing more.
Also, at what point did this "clean up" take place? Because (admittedly
I almost never use more), I don't ever recall this being an issue.
--
redhat-lspp mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/redhat-lspp
