From 011b3214d50b254f5d3bb766d2761f674925f6a6 Mon Sep 17 00:00:00 2001 From: wiz Date: Fri, 16 Nov 2001 11:37:04 +0000 Subject: [PATCH] Sort sections and SEE ALSO. --- sbin/init/init.8 | 36 ++++++++++++++++++------------------ 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/sbin/init/init.8 b/sbin/init/init.8 index ec45b2f9ada5..8e2a56c91962 100644 --- a/sbin/init/init.8 +++ b/sbin/init/init.8 @@ -1,4 +1,4 @@ -.\" $NetBSD: init.8,v 1.23 2001/06/05 11:22:45 wiz Exp $ +.\" $NetBSD: init.8,v 1.24 2001/11/16 11:37:04 wiz Exp $ .\" .\" Copyright (c) 1980, 1991, 1993 .\" The Regents of the University of California. All rights reserved. @@ -305,22 +305,6 @@ If, at bootstrap time, the .Nm process cannot be located, the system will panic with the message ``panic: "init died (signal %d, exit %d)''. -.Sh DIAGNOSTICS -.Bl -diag -.It "getty repeating too quickly on port %s, sleeping" -A process being started to service a line is exiting quickly -each time it is started. -This is often caused by a ringing or noisy terminal line. -.Em "Init will sleep for 10 seconds" , -.Em "then continue trying to start the process" . -.Pp -.It "some processes would not die; ps axl advised." -A process -is hung and could not be killed when the system was shutting down. -This condition is usually caused by a process -that is stuck in a device driver because of -a persistent device error condition. -.El .Sh FILES .Bl -tag -width /var/log/wtmp -compact .It Pa /dev/console @@ -337,9 +321,25 @@ The terminal initialization information file. .It Pa /etc/rc System startup commands. .El +.Sh DIAGNOSTICS +.Bl -diag +.It "getty repeating too quickly on port %s, sleeping" +A process being started to service a line is exiting quickly +each time it is started. +This is often caused by a ringing or noisy terminal line. +.Em "Init will sleep for 10 seconds" , +.Em "then continue trying to start the process" . +.Pp +.It "some processes would not die; ps axl advised." +A process +is hung and could not be killed when the system was shutting down. +This condition is usually caused by a process +that is stuck in a device driver because of +a persistent device error condition. +.El .Sh SEE ALSO -.Xr login 1 , .Xr kill 1 , +.Xr login 1 , .Xr sh 1 , .Xr options 4 , .Xr ttys 5 ,