|Summary:||minicom no longer SGID "uucp", but /var/lock directory is group uucp|
|Product:||[Retired] Red Hat Linux||Reporter:||pfeif|
|Component:||minicom||Assignee:||Cristian Gafton <gafton>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1999-05-19 16:34:42 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description pfeif 1999-05-19 05:25:24 UTC
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 used.
Comment 1 Jay Turner 1999-05-19 14:11:59 UTC
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 16:34:59 UTC
Fixed in dist-6.1 minicom-1.82-6.
Comment 3 Jay Turner 1999-05-27 14:15:59 UTC
*** 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