Date: Tue, 4 Apr 2000 01:03:01 +0900 (JST)
From: Takahiro Kambe <taca@sky.yamashina.kyoto.jp>
Reply-To: taca@sky.yamashina.kyoto.jp
To: gnats-bugs@gnats.netbsd.org
Subject: shutdown(8) from remote machine hangs the client side.


>Number:         9757
>Category:       bin
>Synopsis:       shutdown(8) from remote machine hangs the client side.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 03 09:06:01 PDT 2000
>Closed-Date:    
>Last-Modified:  Mon Apr 03 19:59:51 PDT 2000
>Originator:     Takahiro Kambe
>Release:        NetBSD-current 2000/4/2
>Organization:

	
>Environment:

	
System: NetBSD edge.sky.yamashina.kyoto.jp 1.4X NetBSD 1.4X (CF-M33) #6: Mon Apr 3 15:52:03 JST 2000 taca@edge.sky.yamashina.kyoto.jp:/usr/src/sys/arch/i386/compile/CF-M33 i386




>Description:
	shutdown(8) from remote machine hangs the client side.


	When system shutdown, shutdown(8) execute /etc/shutdown and
	new /etc/rc.d stuff stop most services including network routes
	and finally network interfaces.


	Flushing network routes or Disabling network interfaces hangs
	remote login client which execute shutdown(8).




>How-To-Repeat:
	telnet(1) or rlogin(1) and execute shutdown(8).


		# shutdown -h now


>Fix:
	There are several way to fix.


	o Inhibit shutdown(8) from other than local termina. (Oh, NO!)


	o Make flushing network routes and disabling network interface
	  done when shutdown(8) is executed from local terminal (including
	  console) only.


	o Any other better solution?




>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->bin-bug-people 
Responsible-Changed-By: gnats 
Responsible-Changed-When: Mon Apr 3 19:57:45 PDT 2000 
Responsible-Changed-Why:  
wrong category - assigned to default party for appropriate category. 
>Unformatted: