Before I recently upgraded the processor everything was fine on ANY installation. So - the only conclusion I can draw is there is “something” in Arch or Arch based systems that doesn’t like my setup whereas Debian based systems have no problems with the same setup. The Freefilesync program works absolutely perfectly on any Debian based system under the same conditions as long as I have at least kernel 5.10 installed as a minimum. The program runs but when the ‘start’ button is clicked the whole system crashes with no acknowledgement from any keypress or mouse click however the cursor still moves across the screen normally. I’ve tried pure Arch xfce, Manjaro xfce with the same result. Others have tried with no problems on their systems but mine won’t run Freefilesync correctly. Since I’ve upgraded my processor I cannot get Freefilesync to work correctly. Doing so is not terribly complicated, but again it falls outside the scope of this question.Interesting. The above tests well for me on a plain vanilla 14.04.4 LTS Desktop, but can be further hardened security wise. In the latter case, with this you can still go home in the evening and have yr cake too. # "what" is a cmd or a collection of cmdsĢ) WARNING: messing with sudoers may end up with a user either smiling or creating a security black hole or making himself and others unable to access sudo altogether. # can be a user "user:" or a group ":group"
# "as_whom" specifies under whose guise the cmd(s) are executed # "tags" is the permission granted to "what" is being allowed # "where" is a host or a collection of hosts # "who" is either a group or a collection of users More details on sudoers are outside OP's scope, but for the sake of being a little more complete, just 2 more comments.ġ) RULE PATTERN FOR sudoers # who where = tags:(as_whom) what Visit man sudoers to learn about the grammar and syntax of sudoers rules. Where admin is any user group that contains you and those you authorize to run FreeFileSync with root privileges.
#Freefilesync ubuntu password#
If you don't want to have to enter your sudo password every time yr backup job runs, or if you want it to run unattended, then go to: /etc/sudoers.d/ and sudo-edit the file 10_user or whatever name you choose, with: %admin yr_host = NOPASSWD: /usr/bin/FreeFileSync In that case you'll have to define DISPLAY appropriately. # define local default display and pass it on to any child processĭISPLAY=:0 export DISPLAY may not suit your use case if you are doing remote admin on a distant volume while executing a remote instance of FreeFileSync. ):ĭon't leave it undefined in your script, include for instance: If however you intend to run the job from an automated script, make sure that the variables you use explicitly or implicitly are known in yr execution environment ( cron, udev. If you execute it from cli, the proper syntax is: $ sudo -i -g bruni /usr/bin/FreeFileSync "$"/.FreeFileSync/backup-jobref.ffs_batch. To my knowledge it is not good to preserve rwx oder ownership of files. Id54843 is a directory, deep under Infolog.įreefilesync is running as bruni bruni 8448 1.9 0.2 753820 46684 ? Sl 11:24 1:05 /home/bruni/Downloads/Software/Linux/FreeFileSync/FreeFileSyncįreefilesync may require sudo privileges to backup certain files in the volumes it parses.
Here are the permissions on the top level mount point: ls -lĭrwxr-xr-x 16 bruni users 488 Jun 14 14:19 InfologĪnd here on the directory the lock file should be made ls -lĭrwxr-xr-x 16 bruni users 0 May 31 22:07 id54843
I use Ubuntu 16.04 and Freefilesync 8.2, but I can imagine that this is redundant information. So my question is, why can't freefilesync and how could I solve the particular problem? Please note that this problem is not related to the TLS encryption as it also arises when I do not use https (when I am at office).Īlso note that I am able to create files in the mounted directory from the terminal or even nautilus. However, when trying to sync this folder using freefilesync I get the following error: Cannot set directory lock for "/path/to/mountpoint".Ĭannot write file "/path/to/mountpoint/sync.ffs_lock". For mounting this directory I use the following command: sudo mount -t davfs -o uid=bruni,gid=users /home/bruni/mountpoint I have mounted a webdav folder using webdav as described here.
0 kommentar(er)
