Bug 772747 - wallaby user request
wallaby user request
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: setup (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ondrej Vasik
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-09 16:04 EST by Robert Rati
Modified: 2012-01-10 03:28 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 772745
Environment:
Last Closed: 2012-01-10 03:28:34 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 Robert Rati 2012-01-09 16:04:17 EST
+++ This bug was initially created as a clone of Bug #772745 +++

Description of problem:
I need a user and group created for a package called wallaby.  The user and the group should both be "wallaby", and the user should have a home directory of /var/lib/wallaby.  These are used to own the wallaby service and data files.  The wallaby package currently creates the group/account with:

%pre
getent group wallaby >/dev/null || groupadd -r wallaby
getent passwd wallaby >/dev/null || \
  useradd -r -g wallaby -d %{_localstatedir}/lib/wallaby -s /sbin/nologin \
    -c "Owner of Wallaby service" wallaby
exit 0

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Ondrej Vasik 2012-01-10 03:28:34 EST
Uidgid pair 181:181 reserved in Fedora Rawhide (setup-2.8.47-1.fc17), please modify your %pre section to match with these reserved uid/gid numbers. I do not plan to do an update of setup package in F15/F16 just for this, but it should be safe to use these numbers there - as dynamic system account creation starts above uidgid 200. Closing RAWHIDE.

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