Date: Fri, 6 Jan 1995 20:53:04 +0300
From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su>
To: FreeBSD hackers <freebsd-hackers@freebsd.org>, joerg_wunsch@uriah.sax.de
Subject: Re: {login,getty}.core
Message-ID: <cB0EO3lqF0@astral.msk.su>
In-Reply-To: <199501061555.QAA18202@bonnie.tcd-dresden.de>; from J Wunsch at Fri, 6 Jan 1995 16:55:19 %2B0100 (MET)
References: <199501061555.QAA18202@bonnie.tcd-dresden.de>
index | next in thread | previous in thread | raw e-mail
In message <199501061555.QAA18202@bonnie.tcd-dresden.de> J Wunsch
writes:
>On our network access machine, a 1.1.5 system on a 486, we're
>constantly getting cores from login and getty, triggered by SIGQUIT's,
>as the log tells us.
>After recompiling both programs static (to debug the cores), they
>became `silent'. The only core dump i could get hold of from a static
>binary displayed the signal somewhere in ioctl(), qprobably when
>switching back from raw mode.
>Any explanations? (They are not serious, but annoying.)
I ignore SIGQUIT in getty in 2.x, it can easily come from serial line.
--
Andrew A. Chernov : And I rest so composedly, /Now, in my bed,
ache@astral.msk.su : That any beholder /Might fancy me dead -
FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead.
RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cB0EO3lqF0>