2016-08-04, 01:20
If you're getting a problem with flock then why not mention it rather than try and fix it yourself, which is likely to make the problem worse?
You definitely don't need sudo to run these scripts, just run them as your normal user. If you run them as sudo then your user will be root, you'll be using /root/.ssh for private/public keys and all files created by the scripts will be owned by root. Basically, you'll cause a lot of problems running with sudo, and at no point were you instructed to run the scripts with sudo.
I don't know what files are in your "projects" folder now. Assuming it's a standard Ubuntu system then try running the following to clean up the mess:
(the above assumes your user has uid:gid (user:group) 1001:1001).
The scripts also create temporary files which may be owned by root - you'll need to clean that up to:
If that doesn't work I don't know what else to tell you. It's difficult trying to get someone to follow instructions that they just make it up instead.
You definitely don't need sudo to run these scripts, just run them as your normal user. If you run them as sudo then your user will be root, you'll be using /root/.ssh for private/public keys and all files created by the scripts will be owned by root. Basically, you'll cause a lot of problems running with sudo, and at no point were you instructed to run the scripts with sudo.
I don't know what files are in your "projects" folder now. Assuming it's a standard Ubuntu system then try running the following to clean up the mess:
Code:
sudo chown -R 1001:1001 ~/projects
The scripts also create temporary files which may be owned by root - you'll need to clean that up to:
Code:
sudo rm -fr /tmp/.oebuild.tmp
If that doesn't work I don't know what else to tell you. It's difficult trying to get someone to follow instructions that they just make it up instead.