Bug 739147 - useradd(8) says that -o option is only valid with -o
Summary: useradd(8) says that -o option is only valid with -o
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: shadow-utils
Version: 15
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Peter Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-16 15:50 UTC by Jiri Popelka
Modified: 2011-11-13 05:31 UTC (History)
2 users (show)

Fixed In Version: shadow-utils-4.1.4.3-10.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-13 05:31:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jiri Popelka 2011-09-16 15:50:58 UTC
From useradd(8) man page

-o, --non-unique
   <snip>
   This option is only valid in combination with the -o option.


There should be '-u' instead of '-o'.

Invocation of useradd with -o without -u gives correct warning:
useradd: -o flag is only allowed with the -u flag 


Version-Release number of selected component (if applicable):
shadow-utils-4.1.4.2-13.fc15

Comment 1 Fedora Update System 2011-11-10 16:54:50 UTC
shadow-utils-4.1.4.3-10.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/shadow-utils-4.1.4.3-10.fc16

Comment 2 Fedora Update System 2011-11-11 01:25:04 UTC
Package shadow-utils-4.1.4.3-10.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing shadow-utils-4.1.4.3-10.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-15737
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2011-11-13 05:31:00 UTC
shadow-utils-4.1.4.3-10.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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