Hi Phil,

my gratulation to release of version of fsvs 1.1.17
I know its hard work to satisfy every user request. I hope this release is a step closer to close the small gaps. For me this is the .subversion folder creation using native fsvs. Currently I still go with the password patches which allow me too use a static password.

On last check at http://fsvs.tigris.org I saw that a lot of links to documentation got lost. Is this because of major upgrade of tigris page? IMO a lot of (new) users would profit from getting access to documentation.

I am just playing with the new directory ignore feature which when I understand correctly has a big use for /etc/fsvs because I can specify explicit files to monitor but not the
fsvs folder itself, is that right?

We just recognized a blocking behaviour on debian/ubuntu systems related to base-files package upgrade. The package uses find to check the /etc folder for symlinks (dont know the exact reason,yet) and loops through the fsvs folder, crying when finding a already checked symlink in /etc/fsvs folder.
find: Symbolic link `/etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/task/12569/fd/3' is part of a loop in the directory hierarchy; we have already visited the directory to which it points. find: /etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/task/12569/fd/4: No such file or directory find: /etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/task/12569/fdinfo/4: No such file or directory find: Symbolic link `/etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/task/12569/cwd' is part of a loop in the directory hierarchy; we have already visited the directory to which it points. find: Symbolic link `/etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/task/12569/root' is part of a loop in the directory hierarchy; we have already visited the directory to which it points. find: Symbolic link `/etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/fd/3' is part of a loop in the directory hierarchy; we have already visited the directory to which it points. find: /etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/fd/4: No such file or directory find: /etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/fdinfo/4: No such file or directory find: Symbolic link `/etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/cwd' is part of a loop in the directory hierarchy; we have already visited the directory to which it points. find: Symbolic link `/etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/self/root' is part of a loop in the directory hierarchy; we have already visited the directory to which it points. find: /etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/1/task/1/fd/6: Not a directory find: Symbolic link `/etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/1/task/1/cwd/lib/udev/devices/fd/3' is part of a loop in the directory hierarchy; we have already visited the directory to which it points. find: /etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/1/task/1/cwd/lib/udev/devices/fd/4: No such file or directory find: Filesystem loop detected; `/etc/fsvs/6666cd76f96956469e7be39d750cc7d9/_base/proc/1/task/1/cwd/proc' has the same device number and inode as a directory which is 5 levels higher in the filesystem hierarchy.

quick workaround:
mv /etc/fsvs ~/
apt-get install base-files
mv ~/fsvs /etc/
better workaround:
?

Best wishes,
Gunnar

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to