:maximum_uid => [4294967290, "The maximum allowed UID. Some
platforms use negative UIDs
but then ship with tools that do not know how to handle
signed ints, so the UIDs show up as
huge numbers that can then not be fed back into the
system. This is a hackish way to fail in a
slightly more useful way when that happens."],
So this is a problem on OS X, and I only just noticed it.
$ dscl . read /groups/nobody PrimaryGroupID
PrimaryGroupID: -2
$ ruby -e "require 'etc'; puts Etc.getgrnam('nobody').gid"
4294967294
$ id nobody
uid=4294967294(nobody) gid=4294967294(nobody) groups=4294967294(nobody)
Obviously we can work around this by increasing maximum_uid, but I'm
wondering why we have this setting at all? Is there some other problem
it solves that I'm not aware of?
At least on OS X, the reverse process works fine.
# ls -l /tmp/foo
-rw-r--r-- 1 nigelk wheel 13 Mar 4 14:36 /tmp/foo
# chgrp 4294967294 /tmp/foo
# ls -l /tmp/foo
-rw-r--r-- 1 nigelk nobody 13 Mar 4 14:36 /tmp/foo
--
Nigel Kersten
Systems Administrator
Tech Lead - MacOps
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
