Bug 509938 - /var/lock not writable?
Summary: /var/lock not writable?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: filesystem
Version: 11
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-07 01:05 UTC by Matt Castelein
Modified: 2009-07-07 13:44 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-07 13:44:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matt Castelein 2009-07-07 01:05:17 UTC
Description of problem: I have a program which has recently begun complaining that /var/lock is not writable.  Since it was working before, I can only guess that either modes or owners have changed on /var/lock, or that I had changed them and the update to filesystem-2.4.21-1.fc11.x86_64 changed them back.  I am filing this report in the hopes of finding out which it is.

Version-Release number of selected component (if applicable):
filesystem-2.4.21-1.fc11.x86_64

How reproducible:
always

Actual results:
Program complains, /var/lock is not writable

Expected results:
Normal program execution

Comment 1 Ondrej Vasik 2009-07-07 12:48:09 UTC
Directory /var/lock should have 0775 root:lock . That's expected behaviour. So if you want to write to /var/lock, you should be either root or member or lock group. Could you please add more informations what's wrong from your opinion? Be more specific which program does complain - I guess it's more issue of that program than issue of root:lock 0775 rights on /var/lock.

Comment 2 Matt Castelein 2009-07-07 13:44:45 UTC
OK, if this is normal then the app needs to be modified to add it's non-privileged user to the lock group.  I'll take it up from that side.


Note You need to log in before you can comment on or make changes to this bug.