SUMMARY: Faulty startup script

From: Peter.Stern@weizmann.ac.il
Date: Wed Feb 16 2005 - 10:12:53 EST


I received two immediate answers (do we expect less?):

>From Joe Senulis:

     We put dsmc into /etc/inittab

#
# Following lines start the TSM backup client scheduler
#
adsm::respawn:/usr/bin/dsmc sched > /dev/null 2>&1
#

and from Tom Smith who said it needs a nohup.

Great list.

Regards,
Peter

Original message:
>
> We are running Tru64 v4.0f PK#7.
>
> Our Computing Center which does our backups put in the following startup
> script:
>
> /sbin/rc3.d/S97tsm -> /sbin/init.d/tsm
>
> # more /sbin/init.d/tsm
> #!/sbin/sh
> /usr/tivoli/tsm/client/ba/bin/dsmc sched -quiet > /dev/null 2>&1 &
> /usr/tivoli/tsm/client/ba/bin/dsmcad > /dev/null 2>&1
>
> After booting, I find:
> root 3753 0.0 0.0 4.72M 608K ?? S Feb 13 0:00.01
> /usr/tivoli/tsm/client/ba/bin/dsmcad
>
> but not /usr/tivoli/tsm/client/ba/bin/dsmc sched -quiet
>
> Even if the former does start, it doesn't seem to work.
> However, if I run the script manually after boot, everything is fine.
>
> What are we doing wrong?
>
> Thanks,
> Peter
>
>
> Peter Stern
> Chemical Physics Department
> Weizmann Institute of Science
> 76100 Rehovot, ISRAEL
>
> email: Peter.Stern@weizmann.ac.il
> phone: 972-8-9342096
> fax: 972-8-9344123
>



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:15 EDT