Bug 2922 - minicom no longer SGID "uucp", but /var/lock directory is group uucp
minicom no longer SGID "uucp", but /var/lock directory is group uucp
Product: Red Hat Linux
Classification: Retired
Component: minicom (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Cristian Gafton
: 3087 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 1999-05-19 01:25 EDT by pfeif
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-05-19 12:34:42 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 pfeif 1999-05-19 01:25:24 EDT
In 6.0, minicom is no longer SGID "uucp", but /var/lock
directory is only group writeable and it's group is uucp,
so minicom cannot create the /var/lock/LCK..modem file so
it fails. The only workaround is to run "minicom -s" as root
to change the lock directory, but then other modem software
(such as ppp dialers) cannot know if the modem is being
Comment 1 Jay Turner 1999-05-19 10:11:59 EDT
Verified that in 6.0, /var/lock is indeed not world-writable and
therefore minicom does have problems creating the lock file.
Comment 2 Jeff Johnson 1999-05-19 12:34:59 EDT
Fixed in dist-6.1 minicom-1.82-6.
Comment 3 Jay Turner 1999-05-27 10:15:59 EDT
*** Bug 3087 has been marked as a duplicate of this bug. ***

the default perms on the minicom binary do not allow it to
create lockfiles in /var/lock since /var/lock is not world
writable +t.  5.2's minicom was set gid uucp as this would
allow it to create lock files in /var/lock

bad news: normal uses cannot launch minicom

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