From: Rich Johnston <rjohnston@sgi.com>
To: James Carter <james.carter@bytemark.co.uk>, 705483@bugs.debian.org
Cc: submit@bugs.debian.org
Subject: Bug#705483: xfsprogs: xfs_quota misinterprets usernames with leading digits
Date: Mon, 15 Apr 2013 11:07:08 -0500 [thread overview]
Message-ID: <516C25AC.60506@sgi.com> (raw)
In-Reply-To: <516C12DB.3060806@bytemark.co.uk>
On 04/15/2013 09:46 AM, James Carter wrote:
> Subject: xfsprogs: xfs_quota misinterprets usernames with leading digits
> Package: xfsprogs
> Version: 3.1.4
> Severity: normal
>
> *** Please type your report below this line ***
>
> xfs_quota interprets usernames with leading digits as a numeric UID so,
> for example:
>
> # xfs_quota -c 'quota -h -u 2000ad' /store
> Disk quotas for User test (2000)
> Filesystem Blocks Quota Limit Warn/Time Mounted on
> /dev/sdb1 12K 1G 1G 00 [------] /store
>
> This is returning quota information for the user "test" (UID 2000), rather
> than the user "2000ad".
>
I don't think this is a bug, username must begin with a character
(unless you created the user using NIS or adduser --force-badname).
# Default from /etc/adduser.conf
# check user and group names also against this regular expression.
#NAME_REGEX="^[a-z][-a-z0-9_]*\$"
From adduser man page:
--force-badname
By default, user and group names are checked against the
config‐
urable regular expression NAME_REGEX (or
NAME_REGEX_SYSTEM if
--system is specified) specified in the configuration
file. This
option forces adduser and addgroup to apply only a weak
check
for validity of the name.
Thanks
--Rich
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-15 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 14:46 Bug#705483: xfsprogs: xfs_quota misinterprets usernames with leading digits James Carter
2013-04-15 16:07 ` Rich Johnston [this message]
2013-04-16 8:17 ` James Carter
2013-04-16 12:29 ` Rich Johnston
2013-04-23 13:02 ` Rich Johnston
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=516C25AC.60506@sgi.com \
--to=rjohnston@sgi.com \
--cc=705483@bugs.debian.org \
--cc=james.carter@bytemark.co.uk \
--cc=submit@bugs.debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.