Re: [systemd-devel] Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n
On Do, 28.05.20 15:43, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > Hi! > > Monitoring the messages created when booting SLES12 SP5, I noticed these: > > ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n > systemd[1]: ypbind.service: Control process exited, code=exited status=1 > systemd[1]: Failed to start NIS/YP Clients to NIS Domain Binder. > systemd[1]: ypbind.service: Unit entered failed state. > systemd[1]: ypbind.service: Failed with result 'exit-code'. > systemd[1]: Reached target User and Group Name Lookups. > > The interesting point is that ypbind.service is disabled. So why is > ypbind-systemd-pre complaining about NIS domain not being set? Maybe ypbind-systemd-pre.service has Wants= or Requires= on ybind.service? Either way, this sounds like something to talk to your distro/package of ypbind with. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n
28.05.2020 16:43, Ulrich Windl пишет: > Hi! > > Monitoring the messages created when booting SLES12 SP5, I noticed these: > > ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n > systemd[1]: ypbind.service: Control process exited, code=exited status=1 > systemd[1]: Failed to start NIS/YP Clients to NIS Domain Binder. > systemd[1]: ypbind.service: Unit entered failed state. > systemd[1]: ypbind.service: Failed with result 'exit-code'. > systemd[1]: Reached target User and Group Name Lookups. > > The interesting point is that ypbind.service is disabled. So why is > ypbind-systemd-pre complaining about NIS domain not being set? > And how exactly ypbind-systemd-pre is related to ypbind.service? > (systemd-228-157.9.1.x86_64) > > Regards, > Ulrich > > > > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n
Hi! Monitoring the messages created when booting SLES12 SP5, I noticed these: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n systemd[1]: ypbind.service: Control process exited, code=exited status=1 systemd[1]: Failed to start NIS/YP Clients to NIS Domain Binder. systemd[1]: ypbind.service: Unit entered failed state. systemd[1]: ypbind.service: Failed with result 'exit-code'. systemd[1]: Reached target User and Group Name Lookups. The interesting point is that ypbind.service is disabled. So why is ypbind-systemd-pre complaining about NIS domain not being set? (systemd-228-157.9.1.x86_64) Regards, Ulrich ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
