Bug 58239 - uucp should be in the lock group
uucp should be in the lock group
Status: CLOSED WONTFIX
Product: Red Hat Raw Hide
Classification: Retired
Component: setup (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-01-11 11:15 EST by Joerg Dorchain
Modified: 2014-03-16 22:24 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-11 11:15:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joerg Dorchain 2002-01-11 11:15:25 EST
Description of Problem:
uucico is setuid/setgid to uucp.uucp. it needs write acces to /var/lock in order
to work.
/var/lock is writeable by id root and group lock, not by uucp

Version-Release number of selected component (if applicable):
uucp-1.06.1-31.i386.rpm
filesystem-2.1.6-3.noarch.rpm
setup-2.5.7-2.noarch.rpm

How Reproducible:
Always

Steps to Reproduce:
1.  run uucico

Actual Results:
Fails with "cannot set lock"

Expected Results:
Should run properly

Additional Information:
There are several ways to fix the situation, IMHO adding uucp to group lock is
easiest
Comment 1 Bill Nottingham 2002-01-11 11:57:53 EST
It's intentional that it's not in the lock group, for security reasons.

AFAIK, it's a build error; if you rebuild it (with lockdev-devel installed), it
should work fine.

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