Antw: [EXT] Re: Q: ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n

["Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>]

>>> Lennart Poettering <lennart@xxxxxxxxxxxxxx> schrieb am 28.05.2020 um 22:25
in
Nachricht
<24474_1590697505_5ED01E21_24474_24_1_20200528202504.GA118706@gardel-login>:
> On Do, 28.05.20 15:43, Ulrich Windl (Ulrich.Windl@xxxxxx‑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?

Neither, sorry. Or at least I could not find such.

# systemctl status ypbind-systemd-pre
● ypbind-systemd-pre.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
# systemctl status ypbind
● ypbind.service - NIS/YP Clients to NIS Domain Binder
   Loaded: loaded (/usr/lib/systemd/system/ypbind.service; disabled; vendor
preset: disabled)
   Active: inactive (dead)
     Docs: man:ypbind(8)

BTW: Is it a bug that "systemctl show no-such-service" does not signal any
error (besides maybe ``LoadError=org.freedesktop.DBus.Error.FileNotFound "No
such file or directory"'')?

> 
> 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@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel