Closed l3u closed 6 years ago
Nevermind, it's just a configuration issue. Can be solved by setting <username>
and <groupname>
in vcontrold.xml
. I added the default values along with a comment to the 300 example config (cf. 7106a53fd1c67dbc0fd702cb755537ff1a2ee38e).
Hi :-)
First of all, vcontrold is now part of the official Gentoo Linux repositories (and I maintain the ebuild).
Then: As I installed vcontrold 0.98.5 (via the newly introduced ebuild) on my Raspberry Pi, I ran into some problems that did not exist before. This is most probably due to the privilege dropping patches introduced recently.
The daemon would start but then exit due to the group "dialout" not being there. I added the group, and the daemon started like before. But when I tried to query it, it exited due to missong permission of the device file attached to my optical link adapter. In my case, it's
/dev/ttyAMA0
, owned byroot:uucp
with the permissionscrw-rw----
. I changed (for now) the permissions tocrw-rw-rw-
, and after that, vcontrold ran as before (I was using v0.98.3 before).I'm not sure how to handle this. Could you explain to me what exactly has been changed and what happens? Probably, the ebuild has to add groups and/or users when installing vcontrold. Or I have to patch the config so that it runs out of the box.
Thanks for all help!
Cheers, Tobias