From owner-freebsd-stable Wed Oct 4 16:51:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id 52BBE37B502 for ; Wed, 4 Oct 2000 16:51:49 -0700 (PDT) Received: by border.alcanet.com.au id <115228>; Thu, 5 Oct 2000 10:51:27 +1000 Content-return: prohibited Date: Thu, 05 Oct 2000 10:51:34 +1100 From: Peter Jeremy Subject: "no t_stop, using nottystop" messages To: stable@FreeBSD.ORG Mail-followup-to: stable@freebsd.org Message-Id: <00Oct5.105127est.115228@border.alcanet.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a box running 4-STABLE from mid-August. Last time I rebooted it, it spat out a string of 'no t_stop, using nottystop' messages immediately after starting syslogd. The messages entries are: Oct 5 10:18:10 aalp02 /kernel: Warning:ttyp0: no t_stop, using nottystop Oct 5 10:18:10 aalp02 /kernel: Warning:ttyp1: no t_stop, using nottystop Oct 5 10:18:10 aalp02 /kernel: Warning:ttyp2: no t_stop, using nottystop Oct 5 10:18:10 aalp02 /kernel: Warning:ttyp3: no t_stop, using nottystop Oct 5 10:18:10 aalp02 /kernel: Warning:ttyp4: no t_stop, using nottystop I've never seen these before. Looking at the source, they come from /sys/miscfs/specfs/spec_vnops.c: spec_open(), when t_stop is not initialised for a TTY. Any ideas what would be causing them? Why just on the first 5 PTYs? Why is syslogd(?) opening ptys? Why don't they occur for other PTYs (I've tried logging in 10 times to use later PTYs without any errors). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message