Red Hat Bugzilla – Bug 186974
gkrellm-daemon fails to start because of user/group conflict with LSB
Last modified: 2007-11-30 17:11:28 EST
Description of problem:
gkrellm-daemon's init script attempts to start as user gkrellm. This user is
created in an rpm post script. The problem is gkrellm requests uid/gid 101.
This is in violation of the LSB which only allocates the range 0-99 for staticly
assigned uids. Further, this conflicts with shadow-utils's useradd
configuration which dynamically allocates uid's in the 100-499 range for system
services that can use an install-time (rahter than buildtime) determined uid.
So, in the case where a system administrator has installed two packages which
dynamically add their UIDs in %post scripts before installing gkrellm-daemon,
gkrellmd will fail to add a group for itself.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start with a Fedora Core version that does not have gkrellm-daemon installed
(and doesn't have the gkrellm user/group)
2. useradd -r test1
3. useradd -r test2
4. yum install gkrellm-daemon
5. service gkrellmd start
Starting gkrellmd: runuser: user gkrellmd does not exist
gkrellmd would start
I have not perused the sources of gkrellmd but the man page and usage within the
init script imply that gkrellmd just needs a username and groupname that it can
run as. This is most likely a case where gkrellm should allow useradd to choose
a uid/gid. So the rpm %preinstall script should use groupadd -r gkrellmd and
useradd -r gkrellmd instead of groupadd -g 101/useradd -u 101.
You're right, there is no reference to UID/GID 101 in the sources, any value
would do as long as the username/groupname exists.
I've updated the package to gkrellm-2.2.9 and removed the UID/GIDs
*** Bug 190523 has been marked as a duplicate of this bug. ***
A uid/gid has been resevered for gkrellmd in /usr/share/doc/setup-*/uidgid:
grep gkrellmd /usr/share/doc/setup-*/uidgid
gkrellmd 101 101 / /sbin/nologin
I've removed the gkrellmd entry in setup CVS, this will be fixed when the next setup
package will be pushed.
An updated FC-5 package is on the way