Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*dsmc\s+sched\s+dies\s+on\s+control\-c\!\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*dsmc\s+sched\s+dies\s+on\s+control\-c\!\s*$/: 3 ]

Total 3 documents matching your query.

1. dsmc sched dies on control-c! (score: 1): Author: Al Cheski <Alan_Cheski AT GULF DOT CA>; Date: Fri, 20 Feb 1998 15:35:44 -0600; Howdy, this is a repost since I have tried some suggestions with no luck....I have found that the dsmc sched process under Solaris 2.5.1 and either V2 client or V3 client will die if a control-c is e; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-02/msg00895.html (11,025 bytes)
2. dsmc sched dies on control-c! (score: 1): Author: Bjorn Sandvik <BHS AT STATOIL DOT NO>; Date: Mon, 23 Feb 1998 08:29:39 +0100; We have a startup script written in Bourne shell (and placed under /etc/init.d, with links from /etc/rc2.d and /etc/rc0.d). This script does (among other things as testing and setting of environement; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-02/msg00914.html (11,829 bytes)
3. FW: dsmc sched dies on control-c! (score: 1): Author: Joubert Eugene Datavia <EugeneJo AT TRANSNET.CO DOT ZA>; Date: Mon, 23 Feb 1998 11:09:34 +0200; Hi I hope I understand the question. In our case we use the following command in the inittab "adsm:234:respawn:/usr/bin/dsmc sched -password=oras02 > /dev/null 2>&1" this will ensure that the schedul; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-02/msg00917.html (10,624 bytes)

Current List: 1 - 3
Page: [1]