>> > I can share sample configuration files and a generic, configurable >> > directory sync shell script that I run from crontab if you're >> > interested. >> >> Yes, very interested, please post it. Does this also work when files >> on _both_ >> sides are created, modified and deleted? > > Not quite. It is based on the assumption that one server has the > master copy of data and the other one is slave. However, it's flexible > enough that it can be run on either server. > > In the definition of what directories are to be synchronised, you can > choose whether orphan files (i.e. files present on the slave and not on > the master) will be deleted or not (really does nothing more than > adding the '--delete' option to the rsync command line). > > Still, it's a one-way synchronisation. Still interested?
Yes! > It's kind of a quick-and-dirty hack too... the fact that the shell > script is well documented tends to 'hide' this a bit :-) It assumes > that the module name to be used when connecting to the rsync server is > built from the path name. E.g. when synchronising /var/spool/mail, it > will successively try to use "varspoolmail" then if that fails > "varspool" then "var" as a module name. It then tries to manage > sub-dirs and path names at both ends properly. With rsync, this is > almost black magic! I have been unable to make any sense out of > what path names the rsync server returns when using source or target as > [EMAIL PROTECTED]::module/sub/dir. It's for one dir only, but let me see the script :) -- Ariën Huisken Xilay Software _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
