Well, -V shows it's not good pb-sles9:~ # rpm -V bash SM5....T /bin/sh I suspect it's something that either the group using it did (although they claim they did not) or the vendor security package that they are trying to get to run there.
I set up the link as you suggested and it still doesn't pass: pb-sles9:/bin # rpm -V bash ....L... /bin/sh But the script problems went away. Needless to say, this one will be rebuilt so they can prove their vendor package didn't do it :) Thanks Mark (now go to bed!) Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, September 26, 2006 10:20 PM To: [email protected] Subject: Re: [LINUX-390] SLES9 problem with /bin/sh Marcy, I don't have any good ideas what might have broken the link and/or replaced it with something else (except perhaps a system cracker or an fumbling SA). If rpm -V bash shows that /bin/sh is not valid, then I would: cd /bin mv sh sh.questionable ln -s bash sh rpm -V bash and see if it passes muster after that. If so, "rm /bin/sh" and then perhaps a "rpm -V" on all your packages. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Wednesday, September 27, 2006 12:38 AM To: [email protected] Subject: SLES9 problem with /bin/sh I have 2 servers - both are SLES 9, 31bit. One system has a /bin/sh file and the other has it linked to /bin/bash. The server without the link is getting syntax errors on the startup scripts, I think because of this (it seems not to have sourced /etc/rc.status amongst other things). Both have bash-2.05b-305.14, same kernel. pb-sles9:/bin # ls -al *sh -rwxr-xr-x 1 root root 122743 Jun 30 2004 ash -rwxr-xr-x 1 root root 551548 Mar 24 2006 bash lrwxrwxrwx 1 root root 4 Jan 10 2006 csh -> tcsh -rwxr-xr-x 1 root root 6550 Nov 17 2005 dbginfo.sh -rwxr-xr-x 1 root root 246686 Apr 4 2005 ksh -rwxr-xr-x 1 root root 8585 Nov 29 2005 rescan-scsi-bus.sh -rwxr-xr-x 1 root root 598556 Jun 30 2004 sash -rwxr-xr-x 1 root root 246686 Apr 4 2005 sh lrwxrwxrwx 1 root root 12 Jun 1 15:04 ssh -> /usr/bin/ssh -rwxr-xr-x 1 root root 415739 Nov 29 2004 tcsh pb-sles9:/bin # rpm -qa | grep bash bash-2.05b-305.14 pb-sles9:/bin # rpm -qf bash bash-2.05b-305.14 pb-sles9:/bin # rpm -qf sh bash-2.05b-305.14 veritas-sles9:/bin # ls -al *sh -rwxr-xr-x 1 root root 122743 Jun 30 2004 ash -rwxr-xr-x 1 root root 551548 Mar 24 2006 bash lrwxrwxrwx 1 root root 4 Feb 4 2006 csh -> tcsh -rwxr-xr-x 1 root root 6550 Nov 17 2005 dbginfo.sh -rwxr-xr-x 1 root root 246686 Apr 4 2005 ksh -rwxr-xr-x 1 root root 8585 Nov 29 2005 rescan-scsi-bus.sh -rwxr-xr-x 1 root root 598556 Jun 30 2004 sash lrwxrwxrwx 1 root root 4 Jul 6 11:44 sh -> bash lrwxrwxrwx 1 root root 12 Jul 24 11:28 ssh -> /usr/bin/ssh -rwxr-xr-x 1 root root 415739 Nov 29 2004 tcsh veritas-sles9:/bin # rpm -qa | grep bash bash-2.05b-305.14 veritas-sles9:/bin # rpm -qf bash bash-2.05b-305.14 Any ideas what would have created that link that maybe didn't run on the first server? Rpm -qil shows that /bin/sh came from the bash package. Marcy Cortes ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
