ypbind not enabled after installation
Julien Vion
julien.vion at uphf.fr
Thu Oct 5 16:04:58 CEST 2023
Hi again,
Apparently, it is intended behavior that ypbind is not enabled by default, as it
would hang if /etc/defaultdomain is not defined. But I need to find a way to
enable it automatically once the defaultdomain is fcopied.
Somehow, "systemctl enable" in the script does not work.
> I am currently installing FAI to manage several CS hands-on labs using Debian
> 12
> bookworm.
> Student authentication is managed using NIS. I created a NIS class in FAI
> config, and added the packages nis, unscd and libnss-nis to
> package_config/NIS.
>
> For some reason, the ypbind service is not started nor enabled upon reboot
> after
> installation. It is correctly installed and configured (as long as I can
> figure
> out), but I have to run "systemctl enable ypbind" and "systemctl start ypbind"
> manually on each machine before it starts working.
>
> I tried to add the two lines before to scripts/NIS/90-misc but then I get this
> error during install:
>
> scripts.log:Failed to enable unit, unit ypbind.service does not exist.
>
> I also tried to add
>
> ln -s /lib/systemd/system/ypbind.service /etc/systemd/system/multi-
> user.target.wants
>
> or
>
> /lib/systemd/systemd-sysv-install enable ypbind
>
> in the script instead, but it won't work either. "systemctl enable" will only
> work correctly after first reboot.
>
> I cannot find any other error related to ypbind in the logs.
>
> Any clues? Maybe it is a bug in the Debian ypbind package?
--
Julien Vion
Maitre de conférences
Chef du département Info
IUT de Valenciennes/Cambrai/Maubeuge
LAMIH CNRS
Université Polytechnique Hauts de France
More information about the linux-fai
mailing list