ADSM-L

Re: Boot command failed - AIX

1996-05-28 15:14:40
Subject: Re: Boot command failed - AIX
From: Kelly Root <kroot1 AT TUELECTRIC DOT COM>
Date: Tue, 28 May 1996 14:14:40 -0500
Yes this was in /etc/rc.
According to the instructions my client received from IBM, IBM said NOT to put
any startup commands in /etc/rc. If any of them fail, especially if output is
directed to /dev/console, the boot process will stop. Add to the
/etc/inittab an entry
similar to:

  local:2:wait:/etc/rc.local 2>&1 | alog -tboot > /dev/console

Create /etc/rc.local, chmod 554, and add local start-up commands to it.
After telling my client this they then suggested to investigate a possible ADSM
bug.

Hope this helps. I'm a real novice when it comes to AIX.

At 12:30 PM 5/28/96 EST, you wrote:
>Kelly,
>Was this in /etc/rc or rc.local? I'm fighting a similar problem not related to
>ADSM. I have a couple of third-party license daemons that I tried to start in
>/etc/rc.local in a similar fashion to the ADSM command you're issuing, and the
>boot process hung at that point.
>Just curious.
>.....Ken
>
>Ken Perdue
>kperdue AT vcu DOT edu              Virginia Commonwealth University
>900 East Main Street                     804/828-0556 (voice)
>Richmond, VA 23219                       804/828-0651 (fax)
>My opinions are my own. Who else would claim them?
>"UNIX System Administration:
>It's a dirty job, but somebody told me I had to do it."
>
>
>
>______________________________ Forward Header
>__________________________________
>Subject: Boot command failed - AIX
>Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at 
>Internet-Mail
>Date:    5/28/96 11:56 AM
>
>
>Our ADSM server (v2.1.3) is on MVS. I have an AIX client that cratered his
>RS6K and it refused to reboot. He spent considerable time with IBM Support
>and one of the problems they detected was that the boot command that
>failed was the ADSM startup command. If the command is entered at the
>command line 'nohup dsmc schedule -password=xxxx &' and it fails no
>problem. BUT, if it fails within a boot file it hangs the machine. Is this
a bug
>in ADSM? or do I need to change something?
>
>Received: from VM.MARIST.EDU by MAIL.UCC.VCU.EDU (SMTPLINK V2.11)
>    ; Tue, 28 May 96 11:56:09 EST
>Return-Path: <owner-adsm-l AT VM.MARIST DOT EDU>
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
>   with BSMTP id 9990; Tue, 28 May 96 11:48:48 EDT
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
(LMail V1.2b/1.8b) with BSMTP id 3152; Tue, 28 May 1996 11:48:47 -0400
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8b) with NJE
>          id 8974 for ADSM-L AT VM.MARIST DOT EDU; Tue, 28 May 1996 11:48:44 
> -0400
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
>          V1.2b/1.8b) with BSMTP id 3142; Tue, 28 May 1996 11:48:43 -0400
>Received: from ns.tuelectric.com by VM.MARIST.EDU (IBM VM SMTP V2R3) with TCP;
>          Tue, 28 May 96 11:48:40 EDT
>Received: from R000ivgh ([146.61.20.48]) by ns.tuelectric.com (8.6.9/8.6.9)
>          with SMTP id KAA18180 for <adsm-l AT vm.marist DOT edu>; Tue, 28 May 
> 1996
>          10:55:19 -0500
>X-Sender: kroot1 AT ns.tuelectric DOT com
>X-Mailer: Windows Eudora Light Version 1.5.2
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>Message-ID:  <199605281555.KAA18180 AT ns.tuelectric DOT com>
>Date:         Tue, 28 May 1996 10:55:19 -0500
>Reply-To:     "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>Sender:       "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>From:         Kelly Root <kroot1 AT TUELECTRIC DOT COM>
>Subject:      Boot command failed - AIX
>To:           Multiple recipients of list ADSM-L <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
<Prev in Thread] Current Thread [Next in Thread>