We've installed the V3R1 Mac client on a test machine and noticed what
seems to be an unintentional change: when the scheduler is started, it asks
for a password, as on V2, and goes to sleep; it appears that when it wakes
up, it asks for the password again (in a darkened office, locked for the
night).  Thus, the schedule fails, and the backup along with it.  The
daemon is not being used.  Does this mean that we'll have to put the
password in the preference file of every Mac with an installed client?

Fred Johanson
NSIT
University of Chicago
773-702-8464