dalben

Joking ? No. But if please feel free to explain the humor. If i disable cache_dir then moving through a directory tree will be slow. Slow enough that my cheapo media player will timeout and I need to start from root again. It's also a matter of having the best of both world. Fast directory searches witot a lag for disk spin p when a file is needed. Its not often is I start looking for a file without actually opening a file.

I run cache_dirs and it's made life a little better. I was wondering though if there is a way for cache_dirs to trigger a spin up of the disks when I start browsing through the directories. It's rare for me to be browsing without eventually opening a file which is when the delay kicks in. It would be great if the disks started up in anticipation of a file being opened.

Ah, that I didn't know. That will make things cleaner. Thanks.

dalben, I've rarely used rsync across remote systems so I'm a bit rusty on what to do. How does your example above connect to the remote rsyncd process? Thanks. that worked after I added the password file location into the command. I want to make one change which is to turn the include variable and file into the exclude. I find in my case that a) the list is a lost smaller and b) if I create a new root directory I'll never remember to add it to the backup include list. I'll hack away at that this after noon. Thanks again for the script.

Thanks for this. My rsync backup scripts are so basic that they are a disaster waiting to happen. My requirements are a little different and before I go tying myself in nots I wanted to run a couple of things past you. My destination is on another networked device. I'm assuming the following target is fine: [email protected]::data To gain access to that network device, rsync needs a password. It currently starts like this: rsync --password-file=/mnt/cache/apps/rsync/.rsyncpwd I'm assuming I can change your script to the following without any issues: else rsync --password-file=/mnt/cache/apps/rsync/.rsyncpwd -avih --delete --stats --include-from=$rsyncincludes --exclude=* --log-file=/tmp/$rsynclog $source $target fi Not sure if you feel like coding the location and name of a password file for rsync, but that would be cool. ******************* Thought I would try it before I post. I am getting errors [->] Subject: ### rsync_backup_to_external.sh" ### [->] [->] Error: target backup location ([email protected]::data) does not exist! [->] . [<-] 250 2.0.0 OK 1355316866 o5sm15777877paz.32 [->] QUIT [<-] 221 2.0.0 closing connection o5sm15777877paz.32 The destination is there as my old code works fine: rsync --password-file=/mnt/cache/apps/rsync/.rsyncpwd -vrHltD --delete --stats /mnt/user/data/ [email protected]::data and the logs show it's working. I tried replacing $target with [email protected]::data in your script but I got the same errors. Any ideas ? I've modified both rsync commands in your script to start run with the password file: rsync --password-file=/mnt/cache/apps/rsync/.rsyncpwd -avih --dry-run --delete --stats --include-from=$rsyncincludes --exclude=* --log-file=/tmp/$rsynclog $source $target

UnMENU gives you the status of a preclear.