From nobody  Thu Jan 15 19:51:43 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA19563;
          Thu, 15 Jan 1998 19:51:43 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199801160351.TAA19563@hub.freebsd.org>
Date: Thu, 15 Jan 1998 19:51:43 -0800 (PST)
From: d.bodero@mailbox.uq.edu.au
To: freebsd-gnats-submit@freebsd.org
Subject: init: reports "can't exec getty 'usr/libexec/getty for port ttyv0:" "no such file or directory
X-Send-Pr-Version: www-1.0

>Number:         5507
>Category:       bin
>Synopsis:       init: reports "can't exec getty 'usr/libexec/getty for port ttyv0:" "no such file or directory
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    steve
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          support
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 15 20:00:01 PST 1998
>Closed-Date:    Sun Feb 1 19:43:52 PST 1998
>Last-Modified:  Sun Feb  1 19:44:44 PST 1998
>Originator:     Doug Bodero
>Release:        ver 2.2.5
>Organization:
Trinity Lutheran College, Ashmore, Qld, AUSTRALIA
>Environment:
don't know
??? FreeBSD 2.2.5-PreRel ???

>Description:
At BSD bootup, processing appears to proceed without problems, until the system apparently can't getty.  Every 30 seconds the system constantly attempts the run getty.

A typical error reporint line looks like:
Jan 16 23:58:13 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv0: No such file or directory
>How-To-Repeat:
At every BSD boot.
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sun Feb 1 19:43:52 PST 1998 
State-Changed-Why:  
After repeated attempts to contact the orginator, I can only 
assume this was a pilot error and not a real bug. 
>Unformatted:
