I am using the library dev-libs/libcec which depends on dev-libs/lockdev, and with those permission it is not enough to add the the user to group uucp to allow writing to /var/lock, as group uucp does not have write permissions on /var/run/lock. My current fix at the moment is to create /etc/conf.d/local with the following content:

Without getting into much details, 777 is simply over-allowing.
I would go with 775 (as I'd expect write permissions to be given to the group (uucp)), if I were running into an issue. Not before. _________________MBJr.
buy me a beer

Without getting into much details, 777 is simply over-allowing.
I would go with 775 (as I'd expect write permissions to be given to the group (uucp)), if I were running into an issue. Not before.

I agree with that. But why isn't that default on the install?. I have been unable to locate which program that changes the permissions at boot. They are changed back every time hence the local fix. There much surely be a better (correct) fix than to chmod using /etc/conf.d/local?

Sorry to dig up an old thread. It seems "/run/lock" (which "/var/lock" should be symlinked to) now gets created with owner:group "root:uucp" and permissions "0775", which I guess solves the original problem. However, recent versions of udev (at least the systemd variant) set the group owner of serial ports to "dialout", which means that users now wishing to use the serial ports have to be members of both the "uucp" and "dialout" groups!