I usually do a          nohup dsmc sched > /dev/null &

The nohup stands for nohangup, but I still wouldn't do a control C.  The
nohup will let you exit your session normally, without cancelling the
schedule.

Angel Boles

Systems Support
Win 272-5944
Bell (412) 642-5944
bolesav AT westinghouse DOT com

>----------
>From:  Mark Brown (CC Operations Supervisor)[SMTP:CCMB AT musica.mcgill DOT ca]
>Sent:  Thursday, February 27, 1997 12:01 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Background schedule job and Solaris problem hitting ctrl-c.
>
>Hello,
>
>On Solaris system I start a schedule  like this;
>
>dsmc schedule &
>
>That's fine. It puts some messages on the console about the schedule
>and then sits in the background.
>
>My problem is that if I then doanother task like  cat dsmsched.log
>then hit ctrl-c to to stop viewing the file the darn schedule job
>terminates with a message saying:
>
>>>>>>> Process Interrupted!!  Severing connection. <<<<<<
>
>I then need to restart the schedule. What is going on.
>
>Thank You,
>  Mark Brown, Operations Supervisor
>  McGill University, Computing Centre
>  Phone (514) 398-2321
>  E-Mail --> ccmb AT musica.mcgill DOT ca
>