>Number:         5341
>Category:       misc
>Synopsis:       ttys(5) does not mention sending a SIGHUP to init
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 21 22:05:00 1998
>Last-Modified:
>Originator:     David Brownlee
>Organization:
<a href="http://www.mono.org/">Monochrome</a>
>Release:        1.3.1
>Environment:
System: NetBSD lapton.anim.dreamworks.com 1.3.1 NetBSD 1.3.1 (_LAPTON_) #0: Tue Mar 24 14:27:08 PST 1998 root@lapton.anim.dreamworks.com:/usr/src/sys/arch/i386/compile/_LAPTON_ i386


>Description:
	init(8) re-reads /etc/ttys upon receipt of a SIGHUP. ttys(5) does
	not mention this, which could cause unnecessary anguish for a novice
	administrator.

>How-To-Repeat:
	etc
>Fix:
--- ttys.5.orig	Tue Apr 21 21:42:07 1998
+++ ttys.5	Tue Apr 21 21:48:57 1998
@@ -118,6 +118,22 @@
 will execute
 .Em before
 starting the command specified by the second field.
+.Pp
+After changing the 
+.Nm
+file a
+.Dv SIGHUP
+signal can be sent to 
+.Xr init 8
+with the command
+.Dq Li "kill \-s HUP 1" .
+On receipt of this signal,
+.Xr init 8
+will re-read the
+.Nm
+file and spawn any necessary
+.Xr getty 8
+processes.
 .Sh EXAMPLES
 .Bd -literal
 # root login on console at 1200 baud
>Audit-Trail:
>Unformatted: