Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fetchmail.pl create a lock file inside /var/run instead of /var/lock #101

Closed
piccardi opened this issue Dec 1, 2017 · 3 comments
Closed

Comments

@piccardi
Copy link

piccardi commented Dec 1, 2017

The fetchmail.pl script try to create a lock file in /var/run/fetchmail, but this is removed at every reboot, and to create that directory you need root permission. Using just the canonical /var/lock directory should be preferred, and no privileged user will be needed to create the lock file

@cboltz
Copy link
Member

cboltz commented Dec 1, 2017

I understand your problem, but don't like your solution - and at least on my system, it wouldn't work ;-)

My /var/lock is a symlink to /run/lock, and that is root:lock 775 (openSUSE Tumbleweed, and I'm quite sure that I didn't do anything to change these permissions). So the user running fetchmail.pl would need to be in the lock group.

The better solution would be to ship a tmpfiles.d sniplet that creates /run/fetchmail/ on boot with the correct permissions.

@piccardi
Copy link
Author

Sorry, I did'nt know about that suse choice and I agree: your solution is better.

DavidGoodwin added a commit that referenced this issue Mar 14, 2020
@DavidGoodwin
Copy link
Member

feel free to add in a tmpfiles.d snippet, but in the meantime, I think 8f20c96 is a reasonable solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants