unix: Use flock to ensure exclusive access #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some applications, e.g. picocom, use
flock
to ensure exclusive access to the serial port, but don't seem to use thetiocexcl
ioctl. This means that, without usingflock
, it is currently possible to connect to a port using picocom first, and then connect using this crate. This leads to problem where not all data is received by the Rust application.To avoid this,
flock
can be used to acquire an advisory lock on the port. This will prevent this crate from opening the port when it has already been opened by picocom. Note that the lock is only advisory, meaning that this requires collaboration between applications.Fixes #265.