On Fri, 7 Oct 1994 09:47:46 EDT Lee Maschmeyer said:
>
>Would it help to disable the server before doing the DUMPDB?  That way,
>only the poor sobs that are already on the server would be locked up.
>Still wrong, but with proper notification it might be tolerable.

While it would be interesting to know the answer to Lee's question, I do
not view this as an acceptable "solution" to this problem.  I believe that
the Macintosh ADSM Scheduler client can hang the Macintosh in other situations
where the server is overloaded (we ran into this once, awhile ago).  I would
like to reinforce Wayne's opinion that it is absolutely intolerable for ADSM
to hang up a user's machine under any circumstances.  I can't think of a
faster way to turn off user's interest in using ADSM.  I believe there is a
window of code that is disabled for interrupts, while waiting for a response
from the server.  IMHO, all such windows should have timeouts on them so that
they eventually give up on the server and return control of the Mac (even if
this means aborting the ADSM application).

>The Dos scheduler always ties up the machine, whether the database is
>quiesced or not.  That's its design.  I wish I had something I could put in
>the autoexec.bat that would issue the ADSM (or any other?) command at a
>certain time every night so I'd get an automatic backup just by not turning
>off my machine.  I've checked out several things from SimTel but none of
>them fills the bill.  Does anyone know of such a beast?

No, I don't, but I too would am looking for this type of solution for both
DOS and Windows.  We did find a public-domain "cron" utility for the Mac,
(thanks to prior post by Keith Crabb), which seems to work pretty well, but
we're still looking for something like this for DOS and Windows.  If the
Scheduler didn't use up so much memory, this wouldn't even be an issue (at
least for Windows and Mac).

..Paul