--- Begin Message ---
Subject: |
chown: Does now allow setting user and users login group with numerical user ID |
Date: |
Thu, 21 Nov 2013 12:50:40 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 |
Dear Gnu Team,
First off: Thanks for existing!! :)))
I think I just found a bug in chown... \o/ ;)
Details about my GNU/Linux system:
Debian wheezy stable 7.2
dpkg -S /bin/chown
coreutils: /bin/chown
dpkg -l|grep coreutils
ii coreutils 8.13-3.5 amd64 GNU core utilities
uname -a
Linux seven 3.10-0.bpo.3-amd64 #1 SMP Debian 3.10.11-1~bpo70+1
(2013-09-24) x86_64 GNU/Linux
echo $SHELL
/bin/zsh
I tried:
chown 1001: /tmp/bla
Leading to:
chown: invalid spec: `1001:'
But as 1001 == "me", it should have done a:
chown me: /tmp/bla
(which works just fine).
Is this a bug or a feature ?
... it should be a bug except if there is a technical detail I am
missing here.
Best,
Tormen
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#15945: chown: Does now allow setting user and users login group with numerical user ID |
Date: |
Thu, 21 Nov 2013 08:53:47 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
tag 15945 notabug
thanks
On 11/21/2013 04:50 AM, Tormen wrote:
>
> I think I just found a bug in chown... \o/ ;)
>
> I tried:
> chown 1001: /tmp/bla
>
> Leading to:
> chown: invalid spec: `1001:'
Drop the trailing colon.
> ... it should be a bug except if there is a technical detail I am
> missing here.
If you provide a colon, you MUST also provide a group spec. Per 'chown
--help', the syntax is:
chown [OPTION]... [OWNER][:[GROUP]] FILE...
so these are valid:
chown 1001 /tmp/bla # change owner only
chown :1001 /tmp/bla # change group only
chown 1001:1001 /tmp/bla # change both
but this is invalid:
chown 1001: /tmp/bla # '' is not a valid group
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
--- End Message ---