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

Jump to bottom

Serial port locking needs adjustment for modern distros #15

Closed
GoogleCodeExporter opened this issue Aug 6, 2015 · 2 comments
Closed

Serial port locking needs adjustment for modern distros #15

GoogleCodeExporter opened this issue Aug 6, 2015 · 2 comments
Labels
auto-migrated

Comments

@GoogleCodeExporter
Copy link 

Downstream fedora bug at: https://bugzilla.redhat.com/show_bug.cgi?id=732360

Currently picocom locks /run/lock/ but it would be good if it used a subdir for 
itself or another locking setup. 

Thoughts?

Original issue reported on code.google.com by niri...@gmail.com on 26 Oct 2011 at 8:28
@GoogleCodeExporter
Copy link
Author 

This patch puts UUCP_LOCK_DIR in a separate makefile variable to
allow Linux distributions with different filesystem permission setups
to easily override where piocom stores lock files.
The default behavior remain unchanged.

This patch is meant to fix:
http://code.google.com/p/picocom/issues/detail?id=15
https://bugzilla.redhat.com/show_bug.cgi?id=732360

picocom's existing behavior of placing lockfiles at
/var/lock/LCK..ttyUSB0 fails on Fedora since
/var/lock is a symlink that (eventually) resolves to /run/lock,
which has permissions: drwxr-xr-x. root root /run/lock/
Building picocom with:
make UUCP_LOCK_DIR=/run/lock/picocom
and creating that directory with permissions:
drwxrwxr-x. root dialout /run/lock/picocom/
would allow users in the "dialout" to use picocom without running into
permission denied errors.

Original comment by scottt.tw on 29 Jan 2012 at 2:22

Attachments:

@GoogleCodeExporter
Copy link
Author 

Fixed in r22

Original comment by nick.pat...@gmail.com on 21 Feb 2012 at 5:44

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter