Hi, FSVS 1.1.7 work rather well now, but I have 2 issues related to a rather peculiar setup. As the next version add some features, especially regarding exclusions, I first want to know if these will solve my problems or not.
The infrastructure I'm working on use an NFS server and a pool of web servers that mount the same NFS volumes. The application directory under FSVS control contains 2 NFS mounted subdirectories. * Read-only subdirectories On some servers (front office), the NFS volumes are mounted readonly. Although I was able to setup FSVS correctly the first time. Now that some files have been updated on the back office server (mounting the same volumes in R/W mode) I can't update the fsvs config anymore: ------------------------------------ [EMAIL PROTECTED] fsvs update Updating svn://10.10.3.24/xxxxx to revision 193. An error occurred: Read-only file system (30) in up__set_meta_data: utimes(./settings/siteaccess/admin/content.ini.append.php) ----------------------------------- How can I solve this? I'd say the best solution is to "fsvs ignore" the R/O subfolders on the servers, but is there another solution? * Subtle time differences between servers On the backend servers, the NFS volumes are mounted R/W. - I commited the changes on "backend1" with "fsvs commit". - I try to update "backend2" with "fsvs update" Unfortunately, for the shared folders, FSVS finds that on backend2 some files have had their modification time modified, which is of course not the case. Even if I try to "fsvs revert" the guilty files, they always appear as being locally modified and "fsvs update" refuses to run. Again, is there a solution other than ignoring the shared folders on one of the backends, and thus versionning them on "backend1" only? Regards -- Farzad FARID / Architecte Open Source - Associé Pragmatic Source / http://www.pragmatic-source.com Tel : +33 9 53 19 21 90 / Mob : +33 6 03 70 65 46 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
