Date: Thu, 05 Oct 2000 10:51:34 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: stable@FreeBSD.ORG Subject: "no t_stop, using nottystop" messages Message-ID: <00Oct5.105127est.115228@border.alcanet.com.au>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00Oct5.105127est.115228>