Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

To: Nuno Oliveira <nuno@eq.uc.pt>
Cc: 906436@bugs.debian.org
Subject: Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts
From: Michael Biebl <biebl@debian.org>
Date: Tue, 21 Aug 2018 12:24:03 +0200
Message-id: <[🔎] fca21c43-37f2-364a-a4f4-4a965677721b@debian.org>
Reply-to: Michael Biebl <biebl@debian.org>, 906436@bugs.debian.org
In-reply-to: <[🔎] 20180821090754.GA7098@eq.uc.pt>
References: <[🔎] 20180820124020.GA3344@eq.uc.pt> <[🔎] a129423a-e680-338f-530f-c9f54d179a0e@debian.org> <[🔎] 20180821090754.GA7098@eq.uc.pt> <[🔎] 153451986898.4301.18412692519960151338.reportbug@hilbert.systella.fr>

Am 21.08.2018 um 11:07 schrieb Nuno Oliveira:

> Apparently Network Manager support in NIS was introduced to avoid ypbind
> from being killed by systemd.

That sounds like non-sense and definitely not the root cause of the issue.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to:

References:
- Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts
  - From: Nuno Oliveira <nuno@eq.uc.pt>
- Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts
  - From: Michael Biebl <biebl@debian.org>
- Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts
  - From: Nuno Oliveira <nuno@eq.uc.pt>
- Bug#906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts
  - From: BERTRAND Joël <joel.bertrand@systella.fr>

Prev by Date: Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts
Next by Date: Bug#906436: nis debugging
Previous by thread: Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts
Next by thread: Bug#906436: nis debugging
Index(es):
- Date
- Thread