Hello,
to improve the experience with out Samba packages and especially to address issues with the new Samba AD feature in F27 I would like to request a group ID for Samba.
The group name is not fixed yet, probably 'adadmin'.
If available I would prefer GID 71.
Thanks,
Andreas
We aren't responsible for assigning the actual IDs, but do note that as far as I can tell, GID 71 is already allocated to "realtime". https://pagure.io/setup/blob/master/f/uidgid has:
realtime - 71 - - -
(third field is the reserved GID).
In any case, I don't have any real objections to this though I would like to know how fixing a GID will make any difference. Could you provide a bit of detail as to how the experience is improved, or what issues this would solve?
Metadata Update from @tibbs: - Issue tagged with: meeting
Samba can act as a print server. This means the machine has one or several printers attached via cups. Windows clients require drivers for printers and then a user selects a printer on Windows the driver are automatically installed. But before you can do that someone (an admin) needs to upload printer drivers to the printer server. I would like to have a group you can add users to who are allowed to upload printers. Having a group I could create the drivers directory with 0775 and root:adadmin and then setup the share the following way:
[print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @adadmin root force group = @adadmin create mask = 0664 directory mask = 0775
This way all users part of the group adadmin are able to upload and also update drivers.
There's no problem adding a group for purposes like this - our question is why is it helpful to have a fixed GID rather simply assigning one on install like most packages.
Right; the question is why this needs to have the exact same numeric GID on every system. You would have to create the group in either case in %pre and you don't need any approval to do that unless you absolutely require that the GID be fixed. We don't have all that many unallocated numbers at this point so the bar is pretty high.
As an aside, I wish we could relinquish the allocations somehow. There's an allocation for cyrus-imapd (which I help maintain) which just isn't necessary, and I'm sure there are plenty of other old useless ones in there, too. Though, thinking about it, I think we can actually relinquish them pretty easily. Just switch the packages to do dynamic allocation and then drop the allocation from the list in setup (which is just a text list that's not enforced by anything other than policy as far as I know).
Then I will just go and create one without a fixed gid.
Metadata Update from @orion: - Issue untagged with: meeting - Issue close_status updated to: nothingtodo - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.