Re: Bug#288180: nis kills sparc64
reassign 288180 kernel-image-2.6.8-2-sparc64-smp
thanks
This bug report appears to be a kernel issue: no matter how messed up
NIS gets it shouldn't be capable of causing this kind of damage.
On Sun, Jan 02, 2005 at 09:57:26AM +0000, Beezly wrote:
> Package: nis
> Version: 3.12-3
> Severity: critical
>
> Installing the nis package on my E4500 kills the machine. It seems to
> stop the machine creating new processes althought it's difficult for me
> to tell as I have limited physical access to the machine.
>
> Doing apt-get install nis produces the following...
>
> gold:/usr/sbin# apt-get install nis
> Reading Package Lists... Done
> Building Dependency Tree... Done
> The following NEW packages will be installed:
> nis
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 235kB of archives.
> After unpacking 844kB of additional disk space will be used.
> Get:1 http://mirrors.shef.ac.uk testing/main nis 3.12-3 [235kB]
> Fetched 235kB in 4s (53.7kB/s)
> Preconfiguring packages ...
> Selecting previously deselected package nis.
> (Reading database ... 29539 files and directories currently installed.)
> Unpacking nis (from .../archives/nis_3.12-3_sparc.deb) ...
> Setting up nis (3.12-3) ...
> Setting NIS domainname to: beezly.org.uk
> Starting NIS services: ypbind
>
> The machine becomes inaccessible after loading ypbind and you cannot
> interrupt the terminal, however it IS still possible to ping the
> machine. ssh to the machine gets as far as opening a connection, but no
> further.
>
> Marked critical as it flattens my machine, every application and makes
> it unusable.
>
> Anything you want me to try out, please let me know although it can take
> me a while to get back to you... I have to drive over two hills to get
> to the machine!
>
> Cheers,
>
> Andrew
>
>
>
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
Reply to: