Date: Mon, 12 Jan 2004 15:23:37 +0200 From: Ari Suutari <ari@suutari.iki.fi> To: Josef Karthauser <joe@freebsd.org>, David Malone <dwmalone@maths.tcd.ie> Cc: freebsd-current@freebsd.org Subject: Re: Problems with syslogd under 5.2-RELEASE Message-ID: <200401121523.37948.ari@suutari.iki.fi> In-Reply-To: <20040112124552.GF19402@genius.tao.org.uk> References: <20040112113040.GC19402@genius.tao.org.uk> <20040112113643.GA54144@walton.maths.tcd.ie> <20040112124552.GF19402@genius.tao.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
On Monday 12 January 2004 14:45, Josef Karthauser wrote:
> > Is your console in some wird state? (XOFF, scroll-lock-on, ...)
> Maybe, I'm running a serial console on this machine, and I changed over
> to it at the same time as the problems began (at the same time I
> upgraded to 5.2). The serial console is a remote serial port connected
> to a Cisco box.
I had problems like this (although on 4.x -version). When I changed
the console line in /etc/ttys to this:
ttyd0 "/usr/libexec/getty 3wire.9600" vt100 on secure
It has been working ok since that. I think the magic
is in "3wire.xxxx", it tells getty that there won't be
modem signals available.
Ari S.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401121523.37948.ari>