Displaying 7 results from an estimated 7 matches for "dynamicuser".
Did you mean:
dynamicus
2020 May 04
2
default backend = rid not showing full group information for users
...d', not sure what this actually does, but when I am forced
> to use systemd (e.g. on my rpi), everything works even though I remove
> 'systemd' from the passwd and group lines in nsswitch.conf.
The systemd NSS module handles dynamically allocated users and groups when a
unit has DynamicUser=true. See systemd.exec(5).
--
Magnus Holmgren holmgren at lysator.liu.se
2020 May 04
2
default backend = rid not showing full group information for users
...hen I am forced
> >> to use systemd (e.g. on my rpi), everything works even though I remove
> >> 'systemd' from the passwd and group lines in nsswitch.conf.
> >
> > The systemd NSS module handles dynamically allocated users and groups when
> > a unit has DynamicUser=true. See systemd.exec(5).
>
> Care to say where that would be used ?
Wherever you want, I guess. I think the idea is to isolate network services
better from each other than if you run them as nobody.
--
Magnus Holmgren holmgren at lysator.liu.se
-------------- next part ---------...
2020 May 04
2
default backend = rid not showing full group information for users
...samba wrote:
> > m?ndag 4 maj 2020 kl. 20:45:37 CEST skrev Rowland penny via samba:
> >> On 04/05/2020 19:24, Magnus Holmgren via samba wrote:
> >>> The systemd NSS module handles dynamically allocated users and groups
> >>> when
> >>> a unit has DynamicUser=true. See systemd.exec(5).
> >>
> >> Care to say where that would be used ?
> >
> > Wherever you want, I guess. I think the idea is to isolate network
> > services
> > better from each other than if you run them as nobody.
>
> So you don't actu...
2020 May 04
0
default backend = rid not showing full group information for users
...en I am forced
>>>> to use systemd (e.g. on my rpi), everything works even though I remove
>>>> 'systemd' from the passwd and group lines in nsswitch.conf.
>>> The systemd NSS module handles dynamically allocated users and groups when
>>> a unit has DynamicUser=true. See systemd.exec(5).
>> Care to say where that would be used ?
> Wherever you want, I guess. I think the idea is to isolate network services
> better from each other than if you run them as nobody.
So you don't actually know of a case where it could be used, I will just
stic...
2020 May 05
0
default backend = rid not showing full group information for users
...gt;>> m?ndag 4 maj 2020 kl. 20:45:37 CEST skrev Rowland penny via samba:
>>>> On 04/05/2020 19:24, Magnus Holmgren via samba wrote:
>>>>> The systemd NSS module handles dynamically allocated users and groups
>>>>> when
>>>>> a unit has DynamicUser=true. See systemd.exec(5).
>>>> Care to say where that would be used ?
>>> Wherever you want, I guess. I think the idea is to isolate network
>>> services
>>> better from each other than if you run them as nobody.
>> So you don't actually know of a c...
2020 May 03
4
default backend = rid not showing full group information for users
Which Debian version do you use? Because in either version (0 oer 10) in
nsswitch.conf is wirtten "files winbind" in Debian 9 it's "compat
winbind" and in 10 it's "files systemd winbind" so you removed (I think)
systemd maybe you should put it back in
Am 01.05.20 um 02:12 schrieb miguel medalha via samba:
>> I am trying to use the backend = rid but it
2014 Sep 29
8
Spacewalk? Local repo? Cache?
I have a mix of CentOS 5, 6, and now 7 servers at work. There are enough of them now that it is starting to make sense for them to get updates from an internal source.
I've seen RHN Satellite in years past. It looks like it may be a way to allow Windows admins here (familiar with WSUS) to update Linux boxes. A local repo might be easier to set up, but (as with Spacewalk) it seems like