Dianne,

We had problems with adsm in the /etc/inittab on SOME of our HP Workstations
running HP-UX 9.05.  The adsm process would unexpectedly die.  We resolved
this problem by using the following line:

        adsm::respawn:/usr/adsm/dsmc sched > /dev/null 2>&1

Good Luck,

Mark Dyer

>
> Thanks for the feedback.  I'll pass it on to our Unix guy.
>
> Dianne Sharp
> Operations Analyst
> ISS CUSTOMER SUPPORT
> Ext 4208
>
> >----------
> >From:  Kenneth Yaw[SMTP:kyaw AT CUSA.CANON DOT COM]
> >Sent:  Thursday, 19 December, 1996 5:08AM
> >To:    Multiple recipients of list ADSM-L
> >Subject:       Re: HP Unix Client logs
> >
> >     No.
> >
> >     The Schedule log will not be created.  We solved this problem by
> >     starting ADSM in /etc/inittab on our HP servers:
> >     adsm::once:/usr/adsm/dsmc sched > /dev/null 2>&1
> >
> >     Ken Yaw
> >     Canon USA, Inc.
> >
> >
> >______________________________ Reply Separator
> >_________________________________
> >Subject: HP Unix Client logs
> >Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at ~internet
> >Date:    12/18/96 10:55 AM
> >
> >
> >We are running ADSM Clients (version 2) on HP Unix boxes.  When the
> >Client is rebooted, we start the ADSM Schedule daemon via a script in
> >/sbin/init.d
> >The format of the command is :
> >nohup dsmc schedule -password=xxxx 2>/tmp/adsm$$.log&
> >
> >PROBLEM:
> >As well as the Schedule log being output to the path as specified in the
> >SCHEDLOGNAME option (i.e. /usr/adsm/dsmsched.log), all the same output
> >is being written to the /etc/rc.log
> >
> >QUESTIONS:
> >Does anyone know why this is?
> >If we try and redirect standard output to /dev/null  (e.g.  1>/dev/null)
> > will the normal Schedule log still be created?
> >
> >Dianne Sharp
> >Operations Analyst
> >ISS CUSTOMER SUPPORT
> >Ext 4208
> >
>