/run/user/$UID/keybase/kbfs is a mountpoint
/keybase is a mountpoint
/keybase/private is a symlink -> /run/user/$UID/keybase/kbfs/private
I currently have /keybase in my include list, but only these show up in list-current-files:
Tue Jun 23 08:39:25 2020 keybase
Tue Jun 23 08:39:25 2020 keybase/private
Tue Jun 23 08:39:25 2020 keybase/public
Tue Jun 23 08:39:25 2020 keybase/team
(public and team are also symlinks.)
If I add /keybase/private/dmtucker, nothing changes.
Perhaps the issue is that the symlink reaches across filesystems?
I have been able to get the data that matters backed up by adding /run/user/$UID/keybase/kbfs to my include list, but that seems less than ideal long-term.
@mterry, sorry, I explained that incorrectly...
/run/user/ $UID/keybase/ kbfs is a mountpoint $UID/keybase/ kbfs/private
/keybase is a mountpoint
/keybase/private is a symlink -> /run/user/
I currently have /keybase in my include list, but only these show up in list-current-files:
Tue Jun 23 08:39:25 2020 keybase
Tue Jun 23 08:39:25 2020 keybase/private
Tue Jun 23 08:39:25 2020 keybase/public
Tue Jun 23 08:39:25 2020 keybase/team
(public and team are also symlinks.)
If I add /keybase/ private/ dmtucker, nothing changes.
Perhaps the issue is that the symlink reaches across filesystems?
I have been able to get the data that matters backed up by adding /run/user/ $UID/keybase/ kbfs to my include list, but that seems less than ideal long-term.