not sure when this happened, just noticed it today when working on some vms.
my built-in user systemd-timesync has uid of 101 which is correct BUT it has the primary group of one of my added groups, and NOT systemd-timesync.
i have no idea how this happened or how to fix it since it wont allow me to change the primary group (since it is a built in user). i added systemd-timesync to the auxiliary group in case it needs to see that group for some reason, but im not sure what happened. and the primary group it is in has full access to everything, not something i want any built in accounts acess to.
any suggestions? i guess i can leave it alone, but that would be too easy
this is on truenas scale 24.10.2.1.
thanks
mark
more info
i just found out the cause, just no fix yet
the gid’s are a holdover from 20+ years ago on a readynas nv+ nas who recommended gid’s in that range.
and when we added the freenas servers we copied those gid’s since everything was tied to those already. it worked fine for years
but…when we recently updated from core to scale, scale added a bunch of built-in users/groups. one overlapped with my old gid. kind of surprising to have two gid’s the same number, but here we are… i confirmed this to be the
issue by installing truenas core to a vm to see what users they created, and there was nothing that interferes with my old gid/uid system.
so i added a new gid with the same permission set and users, deleted my old/overlapping gid and rebooted the server hoping for the best.
now the systemd-timesync user says the primary group is nogroup, and the auxiliary group (which i added it to) is systemd-timesync. an improvement but not fixed.
i guess i just need to change the primary group using the cli, but i hate to mess with stuff not knowing whats under the hood.
any suggestions? seems safe enough now that i know what created this issue, but im not an expert here
