home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!news.cso.uiuc.edu!void!ejohnson
- From: ejohnson@void.ncsa.uiuc.edu (Eric E. Johnson)
- Newsgroups: comp.unix.questions
- Subject: Re: Sockets: How do I detect when it has unexpectedly closed
- Message-ID: <ejohnson.727639716@void>
- Date: 21 Jan 93 18:08:36 GMT
- References: <1993Jan13.040639.18416@slate.mines.colorado.edu> <1993Jan15.174830.2021@bvl.pt> <ejohnson.727557988@void>
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: University of Illinois at Urbana
- Lines: 22
-
- ejohnson@void.ncsa.uiuc.edu (Eric E. Johnson) writes:
-
- >Well, I've tried using the signal function to catch SIGPIPE, but my
- >sockets aren't even generating SIGPIPES when I'm writing to them, and
- >yet they're supposedly disconnected.
-
- >Obvious possibilities include... is my signal function set up correctly?
- >Yep, because it does respond to control-c's. Is the signal currently
- >masked out via sigmask? No, I checked that.
-
- >Anything else?
-
- I decided to investigate the source code to netstat. It seems that
- netstat knows more about the state of my socket than I do. I've got the
- source code to netstat, unfortunately, it finds the state of my socket
- by reading memory from the kernel. If I do get find out how to properly
- use the kvm_read command to find the netstat info, I'll post to the
- group.
-
- --
- Eric E Johnson | "The uncontested absurdities of today are the
- ejohnson@a.cs.uiuc.edu | accepted slogans of tomorrow." - Ayn Rand
-