Tino Schwarze wrote at about 09:41:46 +0200 on Wednesday, September 2, 2009: > IMO the easiest approach would be: > - if BackupPC_nightly starts, it acquires a lock, then waits for backups > to complete > - no new backups start until BackupPC_nightly finished > > This should be rather easy since it could be implemented at the central > scheduling code - actually BackupPC_nightly wouldn't be started, just > the flag would be set that it wants to. > > I would like such automatism (configurable, of course) as well since it > just sucks to guess backup periods and to keep some time reserved for > nightly maintenance. >
I like this idea and I agree it would be easy to implement. And by configurable, I assume you mean at a minimum the ability to turn on/off this option. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
