Path: utzoo!attcan!uunet!lll-winken!ames!ncar!unmvax!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: xlsfonts does, sort of, xterm doesn't
Message-ID: <8904051438.AA12756@EXPIRE.LCS.MIT.EDU>
Date: 5 Apr 89 14:38:31 GMT
References: <8904042225.AA08565@dsys.icst.nbs.gov>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 26


    Perhaps I didn't make myself clear, I need a response.

I never thought otherwise.

    Have I used up my quota of
    stupid questions, or are all the gurus on vacation?

The gurus are all exhausted.

    ? I found that somewhere around 4K (pipe size limit?) was about all I
    ? could get out of xlsfonts without it dying or being killed.

We don't see this problem on various OSes here (we don't have SunOS 3.5).  We
have various bug reports for various OSes saying the server is failing to
handle their OS's particular braindamaged error return for the write(v) system
call when various preconceived kernel implementor's notions of how the call
should work aren't met.  It's hard to believe there are so many different
semantics applied to this call, and so many weird interpretations placed on
errors (e.g., returning EWOULDBLOCK is the data is "too big"; geez).  (Now
add SYSV signals and stir ...)  It's almost enough to make one want to attend a
POSIX meeting.

    Is there a way to trace/log all packets to and from the server?

Use xscope.