|
Re: [Veritas-bu] What happened to NO_STANDALONE_UNLOAD / ltid -nsu?
2008-08-15 17:10:37
|
This setting, in fact, can't be in vm.conf (but maybe the upgrade process
scans for known touch files? I dont' recall), and the other way to do it was to
alter the netbackup RC startup script (to pass the -nsu flag to ltid) which also
no longer works. In any case, if it's possible to scan for vm.conf settings and
touchfiles once, there's really no excuse not to do so when EMM starts up on a
master server: again, rule of least surprise.
--
gabriel rosenkoetter
Radian Group
Inc, Unix/Linux/VMware Sysadmin / Backup &
Recovery
gabriel.rosenkoetter AT radian DOT biz, 215 231 1556
Keep in mind that most settings like this could have been in
vm.conf. If they were, then during upgrade nbpushdata adds them to emm
automatically. -Tim
On Fri, Aug 15, 2008 at 3:42 PM, Rosenkoetter, Gabriel
<Gabriel.Rosenkoetter AT radian DOT biz>
wrote:
Aha.
nbemmcmd
-changesetting -DO_NOT_EJECT_STANDALONE 1
-machinename
<whatever>
Because it makes sense for EMM to
fail to get its initial settings from
the touchfiles everybody's already
used to, of course, and to do
everything through a new management
interface.
Don't get me wrong, it IS nice not to have to bounce daemons
in order to
put these things into effect, but it sure seems like a lot of
the EMM
changes violate the law of least surprise...
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|
