Package: cedar-backup2-doc Version: 2.8.1-1 Severity: wishlist In the descriptions of typical configuration process in chapter 4, sections "Setting up ...", there is step 5 in which suggests adding/enabling cron jobs. I think this step is too early: an administrator should first configure Cedar Backup, validate the configuration, test it, (steps 6 thru 8 or 9) and only then if everything works enable cron jobs.
Imagine the situation where configuration process is left in a broken and possibly bad state, for example, on a test run it fills the disk up. If the admin forgets to disable cron jobs he enabled on step 5, this could lead to bad consequencies for the system once the jobs are activated. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.1 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
