<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: /sbin/sh corruption in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672937#M51345</link>
    <description>Did 10.20 still use the /etc/shells file?  Check that also.  If I remember correctly, the users login shell had to be in that file.  If it was deleted, I'm not sure what login would do.&lt;BR /&gt;&lt;BR /&gt;I know 11.x doesn't use the shells file any more.</description>
    <pubDate>Wed, 27 Feb 2002 20:01:54 GMT</pubDate>
    <dc:creator>Eric Ladner</dc:creator>
    <dc:date>2002-02-27T20:01:54Z</dc:date>
    <item>
      <title>/sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672934#M51342</link>
      <description>Hi,&lt;BR /&gt;I have an HP E class running 10.20 which has experienced corruption of /sbin/sh. There's no indication that anything has changed (date, ownership or chksum) yet when attempting to login at the console or telnet as root we receive 'no shell'. The console starts scrolling with the typical getty errors since a respawn of the console isn't possible. Once we provide a 'new' copy of the shell all is back to normal. Anyone have any ideas?</description>
      <pubDate>Wed, 27 Feb 2002 19:33:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672934#M51342</guid>
      <dc:creator>Joe White</dc:creator>
      <dc:date>2002-02-27T19:33:01Z</dc:date>
    </item>
    <item>
      <title>Re: /sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672935#M51343</link>
      <description>I would start by comparing the good and the bad versions of /sbin/sh.&lt;BR /&gt;&lt;BR /&gt;Try things like 'file', 'what', 'strings', etc. to see if anything is different.  Had you installed any patches or anything recently that could have caused this?</description>
      <pubDate>Wed, 27 Feb 2002 19:43:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672935#M51343</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2002-02-27T19:43:18Z</dc:date>
    </item>
    <item>
      <title>Re: /sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672936#M51344</link>
      <description>Hi Joe:&lt;BR /&gt;&lt;BR /&gt;My first question is where are you getting your new copy. Bear in mind that you must have a version from /sbin that is staically linked. The one in /usr/bin won't work. If this is a recurring problem, some process must be copying to /sbin/sh, perhaps an arrant script with stdout redirected to /sbin/sh. In any event, you need to hunt this down quickly. &lt;BR /&gt;Patrick's idea is sound. I wouls save a copy of the bad version and examine it with every tool I could find. In addition to those mentioned, I would add od -c /sbin/sh | pg.&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Feb 2002 19:53:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672936#M51344</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-02-27T19:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: /sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672937#M51345</link>
      <description>Did 10.20 still use the /etc/shells file?  Check that also.  If I remember correctly, the users login shell had to be in that file.  If it was deleted, I'm not sure what login would do.&lt;BR /&gt;&lt;BR /&gt;I know 11.x doesn't use the shells file any more.</description>
      <pubDate>Wed, 27 Feb 2002 20:01:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672937#M51345</guid>
      <dc:creator>Eric Ladner</dc:creator>
      <dc:date>2002-02-27T20:01:54Z</dc:date>
    </item>
    <item>
      <title>Re: /sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672938#M51346</link>
      <description>Hi Joe,&lt;BR /&gt;&lt;BR /&gt;So, does it appear /sbin/sh wasn't actually changed?  The date / time stamp, size, and checksum didn't change?&lt;BR /&gt;&lt;BR /&gt;When you say you provide a 'new' copy of the shell, do you mean you copy a shell to /sbin/sh or do you mean you enter the "sh" command?&lt;BR /&gt;&lt;BR /&gt;Could the /etc/passwd entry for root's shell be bungled?&lt;BR /&gt;&lt;BR /&gt;I don't believe /etc/shells would cause a problem for logging in.  It would for ftp access.&lt;BR /&gt;&lt;BR /&gt;Darrell</description>
      <pubDate>Wed, 27 Feb 2002 20:16:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672938#M51346</guid>
      <dc:creator>Darrell Allen</dc:creator>
      <dc:date>2002-02-27T20:16:13Z</dc:date>
    </item>
    <item>
      <title>Re: /sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672939#M51347</link>
      <description>sorry, should have provided more information. &lt;BR /&gt;   The copy is /sbin/sh from another 10.20 machine. After moving the copied one into place logins are possible again.&lt;BR /&gt;   /etc/passwd for root lists /sbin/sh as the default shell.&lt;BR /&gt;   No new patches have been loaded recently, in fact, nothing has been added to the machine before or since this started. Basically it functions as a mailhost.</description>
      <pubDate>Wed, 27 Feb 2002 20:48:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672939#M51347</guid>
      <dc:creator>Joe White</dc:creator>
      <dc:date>2002-02-27T20:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: /sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672940#M51348</link>
      <description>Well, like they said above, if this is a recuring problem something is writing to the shell and corrupting it..check all at and cron jobs for bad redirection.</description>
      <pubDate>Wed, 27 Feb 2002 22:14:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672940#M51348</guid>
      <dc:creator>Kevin Wright</dc:creator>
      <dc:date>2002-02-27T22:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: /sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672941#M51349</link>
      <description>Doesn't appear to be a script problem. If it were, we'd see some kind of file change. Turns out we may have an inode table problem on /sbin. We've moved the 'corrupted' /sbin/sh to /tmp and 'sh' runs fine there.</description>
      <pubDate>Mon, 04 Mar 2002 17:25:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672941#M51349</guid>
      <dc:creator>Joe White</dc:creator>
      <dc:date>2002-03-04T17:25:53Z</dc:date>
    </item>
    <item>
      <title>Re: /sbin/sh corruption</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672942#M51350</link>
      <description>I too had this problem... I could not find anything out on the HP site... then I noticed it was happening during Netbackup backups.&lt;BR /&gt;&lt;BR /&gt;I found this document that seems to have fixed the problem. You can find this on Veritas's knowledge base searching for "no shell".&lt;BR /&gt;&lt;BR /&gt;Ben&lt;BR /&gt;&lt;BR /&gt;Symptom: &lt;BR /&gt;&lt;BR /&gt;The following error: /sbin/sh get  &lt;NO&gt;   &lt;SHELL&gt;  message for root, is returned when trying to log on or telnet to a machine.  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Exact Error Message:&lt;BR /&gt;&lt;BR /&gt;/sbin/sh get  &lt;NO&gt;   &lt;SHELL&gt;  message for root.&lt;BR /&gt;&lt;BR /&gt;Solution: &lt;BR /&gt;&lt;BR /&gt;This is an OnlineJFS problem.  &lt;BR /&gt;&lt;BR /&gt;The fix is to apply this patch from HP:  PHKL_19530.  &lt;BR /&gt;This patch has been replaced by patch PHKL_20356. &lt;BR /&gt;If this problem is encountered check to see if one of these patches have&lt;BR /&gt;been installed: PHKL_19530 or PHKL_20356.  &lt;BR /&gt;If  &lt;NO&gt; t, install the most recent HP patch that includes both of these patches.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;Tech &lt;NO&gt; te Summary: &lt;BR /&gt;Tech &lt;NO&gt; te Title: The following error: /sbin/sh get  &lt;NO&gt;   &lt;SHELL&gt;  message for root, is returned when trying to log on or telnet to a machine. &lt;BR /&gt;Tech &lt;NO&gt; te ID: 231878 &lt;BR /&gt;Last Updated: August 31 2001 05:59 PM GMT &lt;BR /&gt;This information in this Tech &lt;NO&gt; te applies to: &lt;BR /&gt;Products: NetBackup DataCenter    3.4, 3.4.1 &lt;BR /&gt;NetBackup (UNIX Platforms)    3.1.1, 3.2 &lt;BR /&gt; &lt;BR /&gt;Subject: NetBackup DataCenter - Application - Compatibility&lt;BR /&gt;NetBackup DataCenter - Application - Informational&lt;BR /&gt;NetBackup DataCenter - Application - Patch&lt;BR /&gt;NetBackup v3.2 and prior (UNIX Platforms) - Application - Compatibility&lt;BR /&gt;NetBackup v3.2 and prior (UNIX Platforms) - Application - Informational&lt;BR /&gt;NetBackup v3.2 and prior (UNIX Platforms) - Application - Patch&lt;BR /&gt; &lt;BR /&gt;Languages: English&lt;BR /&gt; &lt;BR /&gt;Operating Systems: HP-UX    10.2 &lt;BR /&gt; &lt;BR /&gt;&lt;/NO&gt;&lt;/NO&gt;&lt;/SHELL&gt;&lt;/NO&gt;&lt;/NO&gt;&lt;/NO&gt;&lt;/NO&gt;&lt;/SHELL&gt;&lt;/NO&gt;&lt;/SHELL&gt;&lt;/NO&gt;</description>
      <pubDate>Mon, 04 Mar 2002 19:13:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sbin-sh-corruption/m-p/2672942#M51350</guid>
      <dc:creator>Ben Roller</dc:creator>
      <dc:date>2002-03-04T19:13:43Z</dc:date>
    </item>
  </channel>
</rss>

