[daip] MNJ

[Eric Greisen]

Andrzej Marecki writes:
 > > mnj.aoc.nrao.edu rolls up its version at approximately 05 hours UT
 > > yesterday it was 050321 to be exact.  Actually we do it at about 10 pm
 > > local time which is 05 UT in winter and 04 in summer.  Running your
 > > MNJ any time after that until the next day gets you the same thing.
 > 
 > Aaaah, I see. That means running MNJ at, say, 06:15 am our local time
 > (which is 8h ahead the AOC local time both summer and winter) would lead
 > to getting everything up-to-date at earliest possible convenience.
 > 
 > So, finally, one quick question. Yesterday MNJ had nothing to update so
 > it ended quickly on mnj.aoc.nrao.edu (05:03:21 UT, as you said).
 > Now assume there are lots of COMLNKs to be done at a given day (like on
 > October 24th when a change in SHISIN.FOR forced a re-compilation of many
 > tasks). Every machine, including mnj.aoc.nrao.edu - obviously - works
 > longer then. Is it safer not to start MNJ before mnj.aoc.nrao.edu
 > assumedly ends all the COMLNKs? In brief: maybe it's better *not* to
 > initialize MNJ earlier than, say, 11pm AOC time i.e. 7am our time....
 > 

The mnj.aoc.nrao.edu machine does not do compiles and links - it just
does the cvs (changed file) machinations.  I would give it up to 15
minutes to do what it needs to but that is about all.

We then run a MNJ here to feed the machines that our local users use.

Eric Greisen