Where I worked one time, to make sure the clients machines were on at night, we asked the workers to REBOOT, not SHUTDOWN their machine when they leave.
That way the M$ machines got fresh reboots regularly (in a kind manner) and the nightly network tasks could do their thing (virus scans, update pushed software, and backups if needed). If worrying about power, let the machines go to 'sleep', but make sure that wakeup on lan is on and working. Just a suggestion. On Thu, 2007-10-04 at 18:36 +0200, Erik van Linstee wrote: > Craig Barratt schreef: > > This means BackupPC_nightly isn't running (or running completely). > > > > Look at the top of the last few LOG files to see if it running, > > or whether it gives an error. > > > If BackupPC_nightly needs to run, then no wonder. This machine is never > on at night :-) > I'll try and see what happens. > > Thanks, > Erik > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > BackupPC-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/backuppc-users > http://backuppc.sourceforge.net/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
