5.0.6 /etc/rc2 - SCO

This is a discussion on 5.0.6 /etc/rc2 - SCO ; A customer just rebooted his 5.0.6a server. We can telnet in, but there are no getty processes running on the console. /etc/rc2.d/messages/prc_sync ends with the normal "Script processing completed for directory (/etc/rc2.d)" but /etc/rc2 is still an active process. Should ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: 5.0.6 /etc/rc2

  1. 5.0.6 /etc/rc2

    A customer just rebooted his 5.0.6a server.

    We can telnet in, but there are no getty processes running on the
    console.

    /etc/rc2.d/messages/prc_sync ends with the normal
    "Script processing completed for directory (/etc/rc2.d)"
    but /etc/rc2 is still an active process.

    Should I kill it, run 'init q' or what?

    --
    JP
    ==> http://www.frappr.com/cusm <==

  2. Re: 5.0.6 /etc/rc2

    On Tue, 19 Sep 2006 14:44:54 -0400, Jean-Pierre Radley
    wrote:

    >A customer just rebooted his 5.0.6a server.
    >
    >We can telnet in, but there are no getty processes running on the
    >console.
    >
    >/etc/rc2.d/messages/prc_sync ends with the normal
    >"Script processing completed for directory (/etc/rc2.d)"
    >but /etc/rc2 is still an active process.
    >
    >Should I kill it, run 'init q' or what?


    Perhaps the dreaded (and infamous) "sleep 1000000" issue?
    http://wdb1.sco.com/kb/showta?taid=1...149186&pgnum=1

    Article claims to be 5.0.5-specific, but I have seen this on 5.0.5 ->
    5.0.7. Never did figure out what triggers this.


    Scott McMillan

  3. Re: 5.0.6 /etc/rc2

    Jean-Pierre Radley typed (on Tue, Sep 19, 2006 at 02:44:54PM -0400):
    | A customer just rebooted his 5.0.6a server.
    |
    | We can telnet in, but there are no getty processes running on the
    | console.
    |
    | /etc/rc2.d/messages/prc_sync ends with the normal
    | "Script processing completed for directory (/etc/rc2.d)"
    | but /etc/rc2 is still an active process.
    |
    | Should I kill it, run 'init q' or what?

    /etc/auth/system/ttys was corrupt. I rebuilt it, and we seem to bew OK
    again.

    --
    JP
    ==> http://www.frappr.com/cusm <==

+ Reply to Thread