Group and Account created automatically in new jail

[Paul van der Zwan]

I just created a new jail on FreeNAS-9.10.2-U1 (86c7ef5).
I noticed one of the accounts and one of the groups I have added are added to the jail:
Jan 29 12:51:07 freenas manage.py: [common.pipesubr:66] Popen()ing: /usr/sbin/chroot '/mnt/datapool/jails/homebridge' /usr/sbin/pw groupadd 'spons' -g '350'
Jan 29 12:51:08 freenas manage.py: [common.pipesubr:66] Popen()ing: /usr/sbin/chroot '/mnt/datapool/jails/homebridge' /usr/sbin/pw useradd 'media' -u '2702' -g 'spons'

Why and why this account and group and not the others ?
As far as I can tell there is nothing special about them.

Paul

 

[Paul van der Zwan]

Hmm found a function called add_media_user_and_group in /usr/local/www/freenasUI/jails/utils.py.
That function looks for an account called 'media' and adds that account and its group to the jails.
That just happens to be the account name I selected for my media share.

Searching the docs I cannot find any reference to this account name and why it's treated this way.
It's not one of the standard accounts AFAIK...

Anybody any explanation ?

Paul

 

[SweetAndLow]

It's added to freenas so people have less permission issues. There is also the same media user in your base users.

Sent from my Nexus 5X using Tapatalk

 

[Paul van der Zwan]

It's added to freenas so people have less permission issues. There is also the same media user in your base users.

Sent from my Nexus 5X using Tapatalk

Aha, I have found the commit on github.
It's dated Aug 10, 2016. My system and my 'media' account predate that by over a year.
So it seems I'm not the only one that thinks having an account called 'media' owning all media files is a good idea.

At least my mystery is solved.
Too bad this 'media' account and its special handling with regards to jails is not documented in the user guide.

Paul