Re: su command failing on RHEL5

2009-06-12 Thread Bob Proulx
Sanjay Kumar wrote:
 [r...@omvm6 ~]# su poo -c cat /dev/tty
 cat: /dev/tty: No such device or address
 ...
 strace is showing below:
 open(/dev/tty, O_RDONLY)  = -1 ENXIO (No such device or address)

The su command appears to be working properly.  The problem shown
above is that your system is missing the /dev/tty device node.
Something has apparently removed it!  You can confirm this by running
the following.

  ls -ld /dev/tty

You could repair your system by creating that device node.  See the
'mknod' documentation for how.

Bob


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


Re: su command failing on RHEL5

2009-06-12 Thread Andreas Schwab
Bob Proulx b...@proulx.com writes:

 Sanjay Kumar wrote:
 [r...@omvm6 ~]# su poo -c cat /dev/tty
 cat: /dev/tty: No such device or address
 ...
 strace is showing below:
 open(/dev/tty, O_RDONLY)  = -1 ENXIO (No such device or 
 address)

 The su command appears to be working properly.  The problem shown
 above is that your system is missing the /dev/tty device node.

If the file were missing, you would get ENOENT.  ENXIO only means that
the underlying device does not exist.  That can either mean that
/dev/tty has the wrong device address (major/minor device number), or
that the process has no controlling terminal.

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
And now for something completely different.


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


Re: su command failing on RHEL5

2009-06-12 Thread Ondřej Vašík
Hello,

Sanjay Kumar wrote:
 [r...@omvm6 ~]# su poo -c cat /dev/tty
 cat: /dev/tty: No such device or address
 open(/dev/tty, O_RDONLY)  = -1 ENXIO (No such device or
 address)

1) su command is not failing
2) cat is working as expected

su -c creates new process in RHEL-5 - which is expected behaviour as it
could cause security problems. This process has apparently no
controlling terminal /dev/tty. There was non-upstream longoption
--session-command added in RHEL-5 to restore RHEL-4 behaviour. Consider
using it in this case.

 Please let us know the fix available or not.

Next time it would be better to use RHEL product support or RedHat
bugzilla. Please try to use it instead of upstream mailing list, if
--session-command is not solving your issue.

Greetings,
 Ondřej Vašík


signature.asc
Description: Toto je digitálně	 podepsaná část	 zprávy
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils


RE: su command failing on RHEL5

2009-06-12 Thread Sanjay Kumar
That I have already checked.

[r...@omvm6 ~]# ls -ld /dev/tty
crw-rw-rw- 1 root tty 5, 0 Jun 13 00:32 /dev/tty
[r...@omvm6 ~]#

I have written, that after copying su executable from RHEL4 on RHEL5, it
is working. There must be some issue with coreutils-5.97. 

Thanks  Regards,
 
Sanjay Kumar
Sr. Software Engg
Symantec Corporation 
www.symantec.com


Office: (020) 4075 4020
Mobile: 919881061153
sanjay_kum...@symantec.com
 



 

-Original Message-
From: Bob Proulx [mailto:b...@proulx.com] 
Sent: Friday, June 12, 2009 5:43 PM
To: Sanjay Kumar
Cc: bug-coreutils@gnu.org
Subject: Re: su command failing on RHEL5

Sanjay Kumar wrote:
 [r...@omvm6 ~]# su poo -c cat /dev/tty
 cat: /dev/tty: No such device or address
 ...
 strace is showing below:
 open(/dev/tty, O_RDONLY)  = -1 ENXIO (No such device or
address)

The su command appears to be working properly.  The problem shown
above is that your system is missing the /dev/tty device node.
Something has apparently removed it!  You can confirm this by running
the following.

  ls -ld /dev/tty

You could repair your system by creating that device node.  See the
'mknod' documentation for how.

Bob


___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils