ADSM-L

Re: dsm scheduler on windows

2005-03-15 06:14:08
Subject: Re: dsm scheduler on windows
From: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 15 Mar 2005 12:12:45 +0100
Paul,

The Acceptor doesn't have to be restarted to pick up the changes in the
dsm.opt. If called upon, the Accepter will start the scheduler services
(for back-up) or web agent (for web gui).


Regards,

Karel
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Paul Fielding
Sent: dinsdag 15 maart 2005 10:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: dsm scheduler on windows

Actually, this brings up a good question that I've never properly
tested.
When running a scheduler service *without* an Acceptor service, then you
most definitely need to restart the service for changes to take place.

But how about when running an Acceptor service?  It makes sense to me
that the Acceptor would need to be restarted whenever an option is
changed that the acceptor must deal with, eg. tcpserveraddress,
schedmode, etc.  Some options, however, are only relevant to the
scheduler service itself, such as exclude lists, dirmc, domain, etc.

Since the scheduler service is started at the appropriate time by the
acceptor, does this imply that the acceptor does not need to be
restarted
for these options?    My personal belief is no - it doesn't need to be
restarted if the changed option is one that the acceptor doesn't touch.
I haven't tested this properly, however.  Anyone proved/disproved this?

Related Note:  When changing items in a Cloptset, is there any
requirement to restart a client scheduler?  Documentation doesn't make
this clear.
Again, my belief is no, it doesn't need to be done, however I have not
tested this....

regards,

Paul

----- Original Message -----
From: "Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, March 14, 2005 3:54 PM
Subject: Re: [ADSM-L] dsm scheduler on windows


> If you make a change in dsm.opt you have to restart the schedule 
> service for scheduled operations to pick up the change.
>
> The schedule service reads the option file at startup.
>
> -----Original Message-----
> From: Mike [mailto:mikee AT MIKEE.ATH DOT CX]
> Sent: Monday, March 14, 2005 4:03 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: dsm scheduler on windows
>
> Trying to set up an easier way to manage the configuration
> (dsm.opt) on windows files. One comment mentioned today is that 
> anytime the dsm.opt changes the dsm sched service must be cycled. Is 
> that true? I thought only the windows equivilant program to dsmc would

> read dsm.opt and as such it is the only think that might need cycling 
> or tweaking of dsm.opt changes.
>
> What's the real answer?
>
> Mike
>

<Prev in Thread] Current Thread [Next in Thread>