On some versions of Unix, you can't start the schedule daemon with a
simple 'nohup dsmc sched &', it  will come back after about 15 seconds as
'stopped'.

        A couple of ways to get around this are:

        - redirect /dev/null into the daemon so it won't desire any more
operator input.
          'nohup dsmc sched </dev/null &'

        - Start the schedule daemon with an 'at' job.
          'at now
           nohup dsmc sched
           ^d'

        This seems to get around the 'stopped' messages we get.

Ben


> -----Original Message-----
> From: Gary Ison [mailto:Gary.Ison AT MAIL.STATE.KY DOT US]
> Sent: Monday, April 24, 2000 9:54 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Digital Unix Questions
>
>
> Hi Folks,
>
>         Anyone out there running the Tivoli client on
> Digital's Tru64 Unix
> client?  I can't seem to keep the scheduler up and running in the
> background.  It starts up, gets the schedule, then stops with
> the "scheduler
> has been stopped" message.  No error log file is created by
> the client.
>
>         The ".op", ".sys", and inc/exc file are syntactically
> correct as
> best I can determine.  The user does not have a "resolv.conf"
> file for DNS
> translations, so the server address is hard coded in dotted
> IP form.  The
> user further informed me they did not define the
> environmental variables.
> The admin command line client works without any problems; I
> did not test the
> b/a client command line other than to do a simple "q mg" to
> set the password
> and look at help text.
>
>         Any hints would be greatly appreciated.  Post them to the list
> server or to my address below.  Thanks.
>
>         Gary L. Ison
>         Governor's Office for Technology
>         101 Cold Harbor Drive
>         Frankfort, Ky.   40601
>         Phone:  (502) 564-8724
>             Fax:  (502) 564-6856
> E-mail: Gary.Ison AT mail.state.ky DOT us <mailto:Gary.Ison AT mail.state.ky 
> DOT us>
>