Back in Time cron job causing hard crash
Bug #1251950 reported by
Roland Hughes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| backintime (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
roland@
Description: OS/4 OpenLinux 13.7
Release: 12.04
backintime-kde 1.0.8-1
Expected unattended backup to work.
What happened was hard system crash
The problem appears to be errors thrown by rsync or one of the other utilities it uses when running as a cron job. When run interactively all that happens is the errors get written to the log. The "scheduled" job must be running at higher priv.
Problem occurred when target was a directory on an NTFS esata drive.
Recommended solution is to have the front end actually check the partition type of the target directory and warn user so they select an ext3 partition as target.
Revision history for this message
| buhtz (buhtz) wrote | #1 |
| Changed in backintime (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
Please re-open and report back if you can reproduce the problem with the latest upstream(!) version Back In Time.
Be aware that the latest version (1.3.3-4) in Ubuntu is out dated.