When not running the current version of timedog as root (so, even when running
as an admin
user), it silently ignores (or simply doesn't know about) files it cannot
access. This also yields a
lower total size of changed files. I don't think this is a common problem
(though maybe plain
users, without admin rights, need sudo all the time), so maybe this could
simply be
documented.
For example, running as an admin user:
~/Downloads/timedog -d 1
==> Comparing TM backup 2009-07-09-213048 to 2009-07-01-140540
Depth: 1 directories
3.2KB-> 3.2KB /.Backup.log
0B-> 0B /.com.apple.TMCheckpoint
788B-> 788B /.exclusions.plist
35.7MB-> 60.3MB [1416] /Macintosh HD/
==> Total Backup: 1421 changed files/directories, 60.34MB
sudo ~/Downloads/timedog -d 1
Password:
==> Comparing TM backup 2009-07-09-213048 to 2009-07-01-140540
Depth: 1 directories
3.2KB-> 3.2KB /.Backup.log
0B-> 0B /.com.apple.TMCheckpoint
788B-> 788B /.exclusions.plist
14.3GB-> 14.4GB [1423] /Macintosh HD/
==> Total Backup: 1428 changed files/directories, 14.36GB
My backup disk is attached to a remote Mac mini, so it's a sparsebundle.
The same issue occurs in TimeTracker. I found it because the logs stated many
GBs were used,
and disk space did indeed decrease by many GBs. However, timedog and
TimeTracker only
reported a much lower value. Using "find . -mtime -10" in the latest backup I
got a warning:
find: ./Macintosh HD/usr/local/mysql-5.0.51a-osx10.5-x86/data: Permission denied
And that folder indeed showed a 11 GB log file, and a 3.5 GB database. This
folder is owned by
user _mysql, group wheel.
Original issue reported on code.google.com by avben...@gmail.com on 10 Jul 2009 at 10:53
Original issue reported on code.google.com by
avben...@gmail.com
on 10 Jul 2009 at 10:53