On 1/6/08, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > I ran some months ago into a case where the uid was expected to be > 'x'. I think that was a cron application, I'm not sure. Anyway, having > the option there is good. > Sounds broken.
> About conflicts, both useradd and groupadd fails when the number is > already assigned to another user, so no worries. > So what would happen in the above cron when using a uid/gid belonging to someone else. > Do you think it's necessary to have a different treatment for system > and user uid/gid's? Or maybe just limit the ids to 100-999? (I can't > see why one would want to use Resources/Requirements to add a normal > user account, so setting a range makes sense). > kdm has an idea about system/user uid. It'll only show user uids. For a long time it would display a ssh user :-) I think having it assume a system id makes sense. Add a user keyword to override. (I, also, can't imagine a use case but its easy to add, just to pass -u to useradd). I can't imagine a difference between system/user groups but once you have code to find next system id, adding it for groups is easy. -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
