Date: Tue, 17 Mar 1998 12:52:57 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: allen campbell <allenc@verinet.com> Cc: questions@FreeBSD.ORG Subject: Re: Broken pipe Message-ID: <Pine.BSF.3.96.980317125204.994e-100000@gdi.uoregon.edu> In-Reply-To: <199803170440.VAA12697@const.>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Mar 1998, allen campbell wrote: > The error is harmless and I now think I understand the reason for it. > I found a clue in the bash(1) FAQ; The FAQ tells the truth. > This sounds like my observations. For some reason, my shell (pdksh) > behaves differently when exec'ed by telnetd(1) as opposed to > xterm(1). I don't know why this difference exists, but it seems > plausible. Pdksh may be altering its behavior based on the > environment it finds itself in. Some shells will do that. I don't know why though. > Is there a program that displays the state of signals for a given > process? Signals are instantaneous; you can't view the status of them and expect to get anything useful. You'd have to run it through gdb and put breakpoints on the signal handler. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980317125204.994e-100000>