Open GoogleCodeExporter opened 9 years ago
It's possible you have run the command from a directory corresponding to a
volume which has been unmounted
(e.g. the TimeMachine volume).
Original comment by jdtsm...@gmail.com
on 30 Nov 2009 at 12:55
I'm having the same issue. I am running timedog from /Mac HD/Applications/,
which is of course mounted and
not a Time Machine volume. When I run "/Applications/timedog -d 5 -l" in
Terminal, I get the following output.
==> Comparing TM backup to
Depth: 5 directories
invalid top directory at /System/Library/Perl/5.8.8/File/Find.pm line 592.
Original comment by johngarr...@gmail.com
on 11 Jan 2010 at 10:10
I am having the same error except mine is for
/System/Library/Perl/5.10.0/File/Find.pm. I am running timedog
from ~/Downloads/ and mounting my sparse bundle over the network and getting to
that image in terminal
before I run timedog.
Original comment by bigmac...@gmail.com
on 20 Jan 2010 at 4:25
Make sure you're inside the backup directory before running the script.
(i.e. not just in the mounted volume base directory.)
For instance, for me, after mounting the Time Machine network SparseBundle in
Disk Utility the backup
directory is in - /Volumes/Backup of <Computer Name>/Backups.backupdb/<Computer
Name>
And timedog should be run with the terminal from that directory.
Original comment by weil...@gmail.com
on 2 Apr 2010 at 11:16
i get the error "invalid top directory at [..]/Find.pm" as well.
i thought it might be due to spaces in the volume name of the TM volume, but i
checked that: it happens for me even on full paths without spaces.
btw, i did cd into the backup directory before issuing the timedog command.
Original comment by hallo...@gmail.com
on 2 Aug 2010 at 3:18
comment #4 fixed the issue for me. Would a patch be accepted to recursively
search from the working directory for a TM volume by default?
Original comment by unrequit...@gmail.com
on 26 Jul 2011 at 6:26
A patch would be welcome. If you have one, please attach it to this bug report.
Thanks.
Original comment by nathanfi...@gmail.com
on 26 Jul 2011 at 1:59
Original issue reported on code.google.com by
dan%appc...@gtempaccount.com
on 12 Nov 2009 at 11:50