Bug 48016

Summary:	Incorrect permissions for /var/lock
Product:	Gentoo Linux	Reporter:	Chris Brown <rf40>
Component:	[OLD] Core system	Assignee:	Gentoo's Team for Core System packages <base-system>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	eckert.thomas, mp26
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Chris Brown 2004-04-16 02:08:53 UTC

Not sure if this is a bug but I beleive the permissions for in the baselayout ebuild for /var/lock should be 775 not 755. Reason to allow users belonging to the uucp group e.g. 'minicom' acces to write there lock to the /var/lock directory

kdir -o root -g uucp -m0755 /var/lock

Reproducible: Always
Steps to Reproduce:
1. Upgrading to version 1.8.10
2.
3.

Actual Results:  
Users could not run minicom, unable to wirte to the /var/lock directory
I had to change the permisions


Sugested fix 
kdir -o root -g uucp -m0755 /var/lock
should be
kdir -o root -g uucp -m0775 /var/lock

Comment 1 Martin Pohlack 2004-08-23 06:47:54 UTC

*** Bug 54070 has been marked as a duplicate of this bug. ***

Comment 2 Thomas Eckert 2004-09-17 11:01:16 UTC

i'm pretty sure that /var/lock should have 775 -- it's common for every terminal
program to place a lockfile there (e.g. app-misc/ckermit does this).

if this is not fixed yet (haven't checked but i stumbled over this one several
times) now would be a good time to squash this bug (it's all toooo easy to fix ;)

Comment 3 SpanKY gentoo-dev

2004-10-05 21:46:13 UTC

updated the ebuild in portage, thanks