I've tested nis nis_3.17.1-1 and nis_3.17.1-2 on a nis client running
buster.
nis_3.17.1-1 works without problems. After a reboot, nis is running.
With nis_3.17.1-2, after a reboot nis is not working. If I log in via
the console and do a systemctl restart nis, ypbind is not
started. But when I jus
On Mon, 20 Aug 2018 22:46:42 +0200 Thomas Lange
wrote:
>
> ypbind is started by /etc/init.d/nis which includes this:
> # Required-Start: $network $portmap $remote_fs
>
> There's not ypbind.service or any other .service file inside the nis
> package. Maybe this is a problem?
nis ships a Sy
ypbind is started by /etc/init.d/nis which includes this:
# Required-Start: $network $portmap $remote_fs
There's not ypbind.service or any other .service file inside the nis
package. Maybe this is a problem?
--
regards Thomas
Package: nis
Version: 3.17.1-2
Severity: important
Dear Maintainer,
I use a NetBSD NIS server for a long time. This servers acts as a NIS server
(master) and some workstations use it (Linux, FreeBSD...).
I have noticed this evening that my Debian Buster was unable to use this server
anymore.
Wh
4 matches
Mail list logo