#64 Lock directory ought to be /run/lock/lockdev instead of /run/lock

[Eric L.]

Hi,

This is a long standing issue but I was too lazy to report it (and as there was no activity on the project, not motivated). Anyway, the issue is there with Fedora 30. The lock directory isn't directly /run/lock but /run/lock/lockdev: this last directory has the correct group lock and rw-rights for it, whereas /run/lock isn't writable by the lock group.

That currently means that I have after each reboot to call sudo chgrp lock /run/lock && sudo chmod g+rwX /run/lock so that bt747 can run (not optimal from a security and UX point of view).

The issue and approach is described in more details at https://github.com/NeuronRobotics/nrjavaserial/issues/60 - this said, the issue is still open after 3 years, so a more pragmatic approach might be required (make the lock directory configurable on the command line?).

Thanks, Eric

[Mario De Weerd]

Hi
I haven't seen this report until now.
The /run/lock directory is effectively used by rxtx and seems to require fixing rxtx.

On the other hand rxtx is not maintained and it might be better to switch to another serial library.
I am not focussing on BT747 anymore and I am willing to include updates to the serial communication bit, but I can't spent time on investigating that issue and a fix in detail.