Just added this line to nsswitch.conf and things are working fine
despite the errors below:
root@xoa-org01:/n/dom.lab/user# grep -Ei auto /etc/nsswitch.conf
automount: files sss
root@xoa-org01:/n/dom.lab/user#
Guessing the messages were not fatal.
Thx,
TK
On 10/19/2019 8:01 PM, TomK via FreeIPA-users wrote:
Hey All,
Are there any recent instructions available for configuring NFS home
directories using ipa-client-automount ?
Currently above command generates:
stderr=
Started rpcidmapd
Starting external process
args=['/bin/systemctl', 'enable', 'nfs-idmapd.service']
Process finished, return code=0
stdout=
stderr=The unit files have no installation config (WantedBy, RequiredBy,
Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
stderr=
Started rpcgssd
Starting external process
args=['/bin/systemctl', 'enable', 'rpc-gssd.service']
Process finished, return code=0
stdout=
stderr=The unit files have no installation config (WantedBy, RequiredBy,
Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
And mount doesn't work.
--
Thx,
TK.