Re: chmod failed: Invalid argument

[Rainer Blome <rainer.blome@gmx.de>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08.02.2016 15:29, Corinna Vinschen wrote:
> On Jan 31 21:24, Rainer Blome wrote:
>> On 28.01.2016 21:40, Corinna Vinschen wrote:
>>>>> On a hunch, do you have old /etc/passwd and /etc/group
>>>>> files
>>>> There is no `/etc/group`, but `/etc/passwd` defines the
>>>> group ID of my user as 513
>> On a Cygwin 2.3.1 on a different machine, `/etc/passwd` also has 
>> 513 in the group column of all users. Yet, when I ask for `id`,
>> I get something like this (translated):
>> 
>> uid=197609(username) gid=197121(None) \ 
>> Groups=197121(None),545(Users),...
> 
> These values make sense.

Please enlighten me. To me it looks as if cygwin or at least mkpasswd
formerly used 513 as the gid for "None", and switched to 197121 at
some point.

I currently do not understand this:

Before I changed gid of my user from 513 to 197121 in /etc/passwd, ls
printed 513 as the group of files in the home directory. After the
change, ls prints "None" as the group. But 197121 is the id of None.
At first sight, this looks like the file group ownership has changed
from 513 to 197121, but I do not see why that should have happened.

>> No doubt. So what kind of maintenance do these files need? Should
>> I have known that they do?
> 
> They should match.  For instance, one problem is if your passwd 
> entry contains a gid not available in either the Windows user DB
> or /etc/group.

Does this mean that if /etc/passwd exists, /etc/group must also exist
(and match)? Or that, if /etc/passwd gives a currently-non-canonical
gid such as 513, /etc/group must exist and define that gid?

Regards, Rainer
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJWuxgTAAoJEI/iM7d3pEsvXnEQAMv8VT5Frv9uvVt7kMuu1SA/
G5K0AnuzS3XCZIZzVgOHls+6XrbOLXVLi6BCf7i2bFm9tBhsT7/U+X4/hfMTMUuz
OsefO6EHmGr+c8jEzm9y2OpU10zf+rsOqgFMD7qnUoJ2kbpUNY+dGKnUOYsQmnZ/
gdUlufQTpAoMsNiEsTlseaiXdGiSS6pCNu7W0HrIn7TI8uPCAxA7zqi5S53a3zpQ
4x7E4+0QS3KxLT5C20RWRhGEx/+efUAWH/G/UJNEdZJ+hc5eG4Abz4Bh7wx0ITuJ
FabuktphYS1RuRxEPJgNpLdUtCervWzNe223aHdcHR+lJygPCcKHBII6h1kU6tiK
vjpvG5wyDvWFewBoAqD3uWwYwo+tMaRMj3rSMXApRcO5IHDgid54Bi7ETwxurfO0
0cMHKuRNsGTO1BZXfZJZBChKRkDDYoF165TvMMMYTop2hUwcGJVl06s48dRnNfc9
h5tgqB3IKBgDb2I1D6GK/yjkMNIH5x9J9Z51qXKFhWs2erosndLy2K0MUk8i23Je
YqYbucBZ+6ynoRKUfUzjtJNL062ZxfBoQHpPJ9PJHJQluagFdkkeBsbxZhdrtYnj
6PNWqTTYWGm+V8Un+LwSqEr1rPDcMtPBkWTxSnjdnBL3iSd85FgXaVrcM+Lc2ptp
Ud3/WslWQqlC69NdFiRK
=kX/M
-----END PGP SIGNATURE-----

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple