From: Etaoin Shrdlu <shrdlu@unlimitedmail.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] pam limits
Date: Thu, 25 Oct 2007 14:25:03 +0200 [thread overview]
Message-ID: <200710251425.03520.shrdlu@unlimitedmail.org> (raw)
In-Reply-To: <1193312749.27662.34.camel@blackwidow.nbk>
On Thursday 25 October 2007, Albert Hopkins wrote:
> Oh do they do that now? That was that nasty Red Hat extension.
While one might agree or disagree about that, IMHO the problem now is
that the options in /etc/default/useradd are ignored. If I run
useradd -D it shows GROUP=100, but running useradd <username> still
creates a new group named after the user and puts the user into it.
After a little search, it seems that the USERGROUPS_ENAB directive
in /etc/login.defs, although not explicitly mentioning this issue, is
the culprit. Setting it to "no" restores the old behavior (putting the
new users into group "users").
Alternatively, looking at the various patches, it seems that a new option
exists (-n), which seems to be the default when -g is not given, that is
not documented in the man page (to see it, "useradd --help" must be
used). This is another case where man pages are not in sync with changes
introduced by patches. Should a bug be opened for this?
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-25 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 11:35 [gentoo-user] pam limits Daniel Iliev
2007-10-25 11:45 ` Albert Hopkins
2007-10-25 12:25 ` Etaoin Shrdlu [this message]
2007-10-25 12:31 ` Etaoin Shrdlu
2007-10-25 12:47 ` [gentoo-user] [SOLVED] " Daniel Iliev
2007-10-25 12:31 ` [gentoo-user] " Daniel Iliev
2007-10-25 12:37 ` Daniel Iliev
2007-10-25 22:02 ` Florian Philipp
2007-10-25 22:59 ` Albert Hopkins
2007-10-25 11:55 ` Etaoin Shrdlu
2007-10-26 7:40 ` Dan Farrell
2007-10-26 7:55 ` Etaoin Shrdlu
2007-10-26 19:02 ` Dan Farrell
2007-10-27 12:16 ` Etaoin Shrdlu
2007-10-25 11:59 ` Dirk Heinrichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710251425.03520.shrdlu@unlimitedmail.org \
--to=shrdlu@unlimitedmail.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox