IMHO, this is not a good architectural direction.

The enterprise solution I believe is:

- An overall software design that allows for in-flight configuration changes 
without any issues;
- A technical implementation that allows for in-flight changes without 
interruption to backup/recovery processes.

Cheers,
Preston.



On 20/04/2012, at 1:26 AM, Eddie Albert wrote:

> My one item for the Networker v8.0, Wish List
> 
> Maintenance LOCKOUT" mode 
> 
> Make it an active BUTTON and an event you can schedule.
> 
> Message to be displayed on all NMC if LOCKOUT is used or scheduled
> 
> "Maintenance LOCKOUT engaged - No new operations will start"
> or
> "Maintenance LOCKOUT engaged" - No new operations will start after 00:01
> on 2012-04-19 until released"
> 
> Then if anyone logs into NMC or heaven forbid NSRADMIN it should display
> at the top of the screen:
> 
> *** MAINTENANCE LOCKOUT ENGAGED ***
> 
> This would allow for truly scheduled maintenance, thoughts?
> 
> Semper fidelis et paratus, /ALE
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type "signoff networker" in the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER