On 11-Jul-2007, at 08:30, Daniel Farnworth wrote:
Or even rsync, very powerful...
Yep, the more I learn about rsync, the better it gets
For example, I have two FreeBSD machines that are servers sitting on
a T1. They have a rsyncd.conf file like this:
[backup]
path = /backup/
comment = Backup
readonly = no
auth users = backup
secrets file = /usr/local/etc/rsyncd.secrets
the secrets file contains a line like:
backup:somelongpassword
and then a crontask like this:
# every 4 hours at 21 after
21 */4 * * */usr/local/bin/rsync -aq --password-file=/var/
rsync.passwd --exclude="/dev" --exclude="*.mov" --exclude="*.avi" --
delete --delete-excluded / server1::backup/server2
these are setup identically on each amchine, so each one backs up to
the other's /backup
the file /var/rsync.password contains the simelongpassword for the
other server (the passwords are different for each server)
The only problem I ever have with this setup is that sometimes the
list of files that have changed is too long and rsync errors out.
When this happens, I have to go in and manually sync /usr/home or
something to get the list of changed files down to a manageable size.
I know for anyone who uses rsync much this is still beginners stuff,
but I found it amazingly useful once I figured it out.
I have a similar, though not reciprocal, setup to sync my wife's
files to my machine, but that is not setup to be automated, I just
run it manually when I think of it, which is usually sometime between
once a day and once a week. I've just never bothered to enable rsync
--daemon on my OS X
rsync -Eav --exclude="*ache*" --exclude="*Trash/" [EMAIL PROTECTED]:. /Users/
The information contained in this communication is intended solely
for the use of the individual or entity to whom it is addressed and
others authorised to receive it.
This is really rather rude to send to a list. Not to mention that
sending it to a obviously public list almost certainly diminishes any
(mythical) force this clause might otherwise have. For the record,
any email that arrives in MY inbox is considered to be public and I
will, at my sole discretion, share it with anyone I wish. If you
don't like it, don't send me email. For the record, almost every
mailing list in existence is archived publicly somewhere (whether you
know it or not), so trying to pretend an email to a such a public
venue is any way private is a bit like pretending the add copy on a
Billboard in Time's Square is private, only less so.
And I don't care if it's your company's policy to add that to all out
going mail. If it is, your company policy is stupid and broken and
needs to be beaten into submission with a sturdy lead pipe. Feel
free to forward my comments to whomever is in charge of company
policy, and they can even contact me off list at kreme
[EMAIL PROTECTED] (real address, camel case optional).
--
Spontaneity has its time and place.
--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
