:: [DNG] systemd killed the NIS star […
Página Inicial
Delete this message
Reply to this message
Autor: Alessandro Selli
Data:  
Para: dng
Tópicos Antigos: Re: [DNG] Request for comments - training room
Assunto: [DNG] systemd killed the NIS star [was: Re: Request for comments -training room]
On 03/12/18 at 14:51, Bruce Ferrell wrote:
> On 12/3/18 5:22 AM, g4sra wrote:
>> >From my perspective, this topic has had some very interesting
>> contributions. Thank you all whom have contributed.
>>
>> To pick out just one as an example, I had considered NIS\YP to be (or
>> rather didn't consider because) all but defunct, and not taken it's
>> simplicity and reliability over other methods into consideration.
>
> NIS/YP is especially interesting for me as something long unused.



  Sorry to bring you these sorry news, people, but Dr. Nikolaus Klepp is
right: NIS really has kicked the bucket:


https://tracker.debian.org/news/1001786/nis-removed-from-testing/


nis REMOVED from testing


        News for package nis <https://tracker.debian.org/pkg/nis>


  * *From*: Debian testing watch <noreply@???>
    <mailto:noreply@release.debian.org>
  * *To*: <nis@???> <mailto:nis@packages.debian.org>
  * *Date*: Thu, 08 Nov 2018 04:39:20 +0000
  * *Subject*: nis REMOVED from testing


FYI: The status of the nis source package
in Debian's testing distribution has changed.

  Previous version: 3.17.1-3
  Current version:  (not in testing)
  Hint: <https://release.debian.org/britney/hints/auto-removals>
    Bug #834298: nis: Can't ypbind




Interesting read:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834298


From: Elimar Riesebieter <riesebie@???>
To: Mark Brown <broonie@???>
Cc: 834298@???
Subject: Re: nis: Can't ypbind
Date: Tue, 16 Aug 2016 13:52:35 +0200


control reopen +1

* Mark Brown <broonie@???> [2016-08-16 12:11 +0100]:

> On Sun, Aug 14, 2016 at 12:02:06PM +0200, Elimar Riesebieter wrote:
>
> > since 3.17-35 I can't bind to my nisserver anymore. Downgrading to
> > 3.17-34 succeeded. Please notice:
>
> This appears to be some change that's systemd related, AFAICT it works
> fine outside of systemd but gets killed when running inside systemd.
> I'm assuming that the dbus integration was causing systemd to notice
> that it was still running.


My server is a sysvinit system. Can't bind from either a sysvinit
Desktop nor a systemd Desktop the sysvinit server. Nevertheless why
don't we update to ypbind-mt-1.38?

Elimar



--
Alessandro Selli <alessandroselli@???>
VOIP SIP: dhatarattha@???
Chiave firma e cifratura PGP/GPG signing and encoding key:
BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE