Subject: bin/12900: mtree: dev/tty: Device not configured
To: None <gnats-bugs@gnats.netbsd.org>
From: None <anne@alcor.concordia.ca>
List: netbsd-bugs
Date: 05/10/2001 10:18:01
>Number: 12900
>Category: bin
>Synopsis: mtree: dev/tty: Device not configured
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu May 10 10:18:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Anne Bennett
>Release: 1.5
>Organization:
Concordia University
>Environment:
NetBSD eridani.concordia.ca 1.5 NetBSD 1.5 (ERIDANI) #1: Tue Mar 20 15:48:34 EST 2001 anne@eridani.concordia.ca:/big/sources/usr/src/sys/arch/i386/compile/ERIDANI i386
>Description:
When "mtree" is called from cron (well, from "security", which is
called from "daily", which is called from cron), it says this on
standard error:
mtree: dev/tty: Device not configured
The above complaint ends up in the mailed "daily output" report.
When "mtree" is called interactively, no such problem occurs.
Additional notes: this happens with the system pretty much "out of
the box". I think I've seen it on earlier revisions of the O/S (1.4)
but I haven't bothered to report it until now. In case it makes a
difference, I am mounting "fdesc" on /dev.
>How-To-Repeat:
Call mtree interactively:
mtree -e -p / -f /etc/mtree/special
It should not complain.
Now call it from "at":
at now +1minute
mtree -e -p / -f /etc/mtree/special
You should receive mail with the complaint:
mtree: dev/tty: Device not configured
>Fix:
No idea! Sorry.
>Release-Note:
>Audit-Trail:
>Unformatted:
X-Send-Pr-Version: www-1.0