Bug 118630 - rexec fails with "Invalid Argument"
rexec fails with "Invalid Argument"
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rsh (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Karel Zak
Ben Levenson
: 142065 (view as bug list)
Depends On:
Blocks: 132991
  Show dependency treegraph
Reported: 2004-03-18 09:34 EST by Chris Van Hoof
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-18 09:03:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Van Hoof 2004-03-18 09:34:15 EST
Description of problem:
rexec fails on RHEL3 when connecting to any other distro... ( rhl
tested ) with "invalid argument"

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

How reproducible:

Steps to Reproduce:
1.Add host to .rhosts 
2.Add rexec to /etc/securetty
3.Execute rexec

Actual results:
user1@host1> rexec host1 ls 
rexec: Invalid argument 

Expected results:
Normal rexec results.

Additional info:

Similar to bug 100976 on RHL
Comment 1 James McDermott 2004-04-07 12:44:40 EDT
Other interesting info, the -a option appears to "fix" the problem...
or substituting rsh seems to work too.
Comment 3 Pancrazio `ezio' de Mauro 2004-06-02 04:43:35 EDT
As a workaround:

LD_ASSUME_KERNEL=2.4.19 rexec <arguments>
Comment 4 Tomas Mraz 2004-11-16 08:22:56 EST
I see this with FC 3 as well. The problem is that the rexec calls
sigaction on every signal < NSIG. But one of the calls will fail.
The easiest fix would be to simply ignore failed sigaction call.
Comment 5 Karel Zak 2004-11-17 12:19:57 EST
Fixed in devel branch (FC4) and will fixed in RHE-3-U5.
Comment 6 Karel Zak 2004-11-23 02:38:25 EST
Fixed in RHEL-4 too.
Comment 7 Karel Zak 2004-12-07 03:15:10 EST
*** Bug 142065 has been marked as a duplicate of this bug. ***
Comment 8 Tim Powers 2005-05-18 09:03:12 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.