Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1405 - linuxconf and netconf alter permissions of /var/lock/
linuxconf and netconf alter permissions of /var/lock/
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-03-02 19:11 EST by jeremy.laidman
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-04-09 23:06:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description jeremy.laidman 1999-03-02 19:11:06 EST
I have a particular requirement to set /var/lock/ to be
writeable by the mail group.  However if I run linuxconf or
netconf and "activate changes", even if I don't select any
changes, the ownership of /var/lock/ is changed to
uucp.root/755.  This breaks my application and I don't see
any reason why linuxconf needs to do this.
Comment 1 Michael K. Johnson 1999-04-09 23:06:59 EDT
One of linuxconf's standard behaviours is to be a second guard
watching over system file and directory permissions.  You can
tell linuxconf the new permissions you want to use and it will
quit annoying you like this.
Control/Control files and systems/Configure all configuration files
is the path you need to take to make these kinds of changes.

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