> (Jun 16 2005 11:24) Ariën Huisken wrote: >> Ok, so the idea is not to use a networked file system because of the >> slow DSL speed. The goal for these servers is to have one dir on both >> sides where users can put and modify files, and a nightly batch to >> sync those two, so users can work at full local speed during the >> daytime and have all files on the local server. >> >> My idea was to rsync both sides, but its a problem when someone >> deletes a file. Maybe it is a good idea to prevent users from >> deleting files, since the purpose of these share is to archive >> documents and should not be deleted. >> >> The fact that a file created one one side isn't immediatly copied to >> the other side is no issue, the next day is fine, because its for >> backup and archiving only. The customer wants a really safe backup to >> another location and keep the DSL traffic as low as possible. > > It's also a problem when both sides are 'masters' not only with deleting > files, but when editing as well. > > rsync does not _merge_ changes it _makes_ changes. > > With cvs for example you merge the changes in a file when two people has > edited that file on separate ends. With rsync the one file on the > 'sending' side will replace the content of the file on the 'receiving' > end. Shorly that means that people on different servers cannot work on > the same files the same day. > > And no, cvs is no good either, unless the files are pure text. :)
Ok, so the only way of doing this would be to prevent users from modifying AND deleting files, or to have two shares: One left-side (read-only for right) and one right-side (read-only for left) and sync them both. Correct? -- Ariën Huisken Xilay Software _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
