On 9/16/2005 4:37 PM, Eric A. Hall wrote: > Two of the groups can be managed while the other two cannot. For example, > http://www.ehsco.com/misc/samba/umgr-admins.gif shows that the "Admins" > group can be opened but http://www.ehsco.com/misc/samba/umgr-users.gif > shows that the "Users" group cannot ("The group name could not be found"). > Similarly, the "LM Hosts" group can be opened but the "Nobody" group > cannot. All of these groups DO show up in various places (like security > dialogs, and in the USRMGR list obviously) but they can't be viewed for > editing in USRMGR.
Are there reserved group names? I was poking around at something else and noticed that "net rpc group display users" and "net rpc group display nobody" failed with "Couldn't list alias members", which are the same groups broken above. I renamed the groups and now they are apparently working fine, both locally and with usrmgr alike. I can kind of understand why "nobody" wouldn't work (there's a nobody user, and there are "nobody" entries in the local passwd and group files [which I'm not using, but add to the problem matrix]). Users appears to be treated as a built-in group tho. Further of interest, "admins" works fine as a groupname, which conflicts with the built-in thinking. Immediate thought that's left after all this: they are reserved names? -- Eric A. Hall http://www.ehsco.com/ Internet Core Protocols http://www.oreilly.com/catalog/coreprot/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
