Hello all,
I've set up FFS on a home linux box to mirror to an external USB HD, running nightly via crontab. I've configured 10 parallel file operations. Nothing else on the linux box and no other computers use the USB HD. In addition to my home dir, I'm mirroring some files in /etc and /usr. FFS is issuing warnings because it doesn't have perms to write the lock file to /etc or /usr. Should I:
1. config FFS to start via sudo OR
2. config FFS to not use lock files OR
3. something else entirely?
TIA
launch FFS via sudo or config FFS to not use lock files or?
- Posts: 2
- Joined: 13 Mar 2026
-
- Posts: 2978
- Joined: 22 Aug 2012
If you want to use lock files, the user under which credentials you run the FFS instance should have write-access to all base locations involved in your sync.
Obviously that user can be SUDO, but also another user you provided sufficient privileges.
FFS lock files protect against other FFS sync tasks simultaneously performing a sync on the same data, (see the description of the LockDirectoriesDuringSync flag). If you don't need that protection, you can set the LockDirectoriesDuringSync flag to False.
If you want/need the protection that the FFS lock-files provide, but do not want to run as SUDO or assign write access to system your system folders, you can act as explained in this thread. Although that thread is about the use of the sync.ffs_db, the same approach should work for the lock-files.
Obviously that user can be SUDO, but also another user you provided sufficient privileges.
FFS lock files protect against other FFS sync tasks simultaneously performing a sync on the same data, (see the description of the LockDirectoriesDuringSync flag). If you don't need that protection, you can set the LockDirectoriesDuringSync flag to False.
If you want/need the protection that the FFS lock-files provide, but do not want to run as SUDO or assign write access to system your system folders, you can act as explained in this thread. Although that thread is about the use of the sync.ffs_db, the same approach should work for the lock-files.
