Yes, this is the desired behavior. Newer version will include ".gvfs" in
default excluded patterns (but the user can always change that), but
this is only for new installs (so you have to add it yourself).
** Changed in: backintime
Status: New => Confirmed
** Changed in: backintime
Status: Confirmed => Won't Fix
** Changed in: backintime
Status: Won't Fix => Fix Committed
--
BIT silently backing up mounted ftp-share
https://bugs.launchpad.net/bugs/512780
You received this bug notification because you are a member of Back In
Time Team, which is subscribed to Back In Time.
Status in Back In Time: Fix Committed
Bug description:
Back in Time is set to backup my home directory, including hidden files. I
connected to an ftp-server with nautilus. Shortly afterwards BIT started
copying a lot of data, as it was backing up the mounted ftp-share. It think the
mount point is ~/.gvfs/SOME_NAME. I don't know whether this is desired behavior
or not, but it copied gigabytes from the ftp-share and that was certainly not
what I wanted. Maybe by default Back in Time should ignore mounted ftp/ssh/....
shares?
_______________________________________________
Mailing list: https://launchpad.net/~bit-team
Post to : bit-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~bit-team
More help : https://help.launchpad.net/ListHelp
