severity 890994 wishlist
tags 890994 + wontfix
quit
As explained by Mark, NIS is not tought for supporting intermittently
connected clients. Also, in the next releases nis services will use
systemd units and that would be used to switch off ypbind if the client
is not connected to a netẇork.
For that purpose, it will be enough:
systemctl enable systemd-networkd.service systemd-networkd-wait-online.service
And then add
After=systemd-networkd-wait-online.service
Wants=systemd-networkd-wait-online.service
to the (future) ypbind.service. That should work even with DHCP.
But it solves only partially the issue and not in general. What if you connect
to another network? What if you are multi-homed? What if the NIS client
is a laptop hosted in multiple variable networks, with more than one domain?
NIS is simply not tought for this use cases, it is an old beast of the 80s.
The simplest thing to do is using ad hoc scripts to on/off the service
on the basis of local needs, it is simply not possible supporting
all possible settings.
On Wed, Feb 21, 2018 at 01:04:33PM +0100, adrien moulin wrote:
Package: nis
Version: 3.17.1-1+b1
Severity: normal
Dear Maintainer,
On stretch when i start without network, the computer is very slow to
launch the graphical interface and when i try to login on tty console there
are important latency.
After research the origin of the problem, i found that /etc/nsswitch.conf
tried to bind nis because ypbind is launch but without network it can't do
it. It seems there are no timeout on this.
I usually use laptop with nis client, on Jessie the nis.service do not
start when the network cable was out but on Stretch it start with or
without network cable. (on the laptop there are a new installation of
debian not a distupgrade)
The solution i have found is not very nice, i had in /etc/init.d/nis when
the process is backgrouned a killall ypbind.
I hope there are an other solution with systemd but i can't find out for
now.
--
Francesco P. Lovergine
