Article View: alt.games.gb
Article #374Re: tac command
From: A Ghost Walking in the Shadows
Date: Thu, 31 Dec 1992 08:39
Date: Thu, 31 Dec 1992 08:39
20 lines
1283 bytes
1283 bytes
In article <23129@venera.isi.edu> rlewis@venera.isi.edu (Roger Lewis) writes: > >By the way, is there a setting that allows that buffer to be larger? > >Is <output flushed> a message that is generated by the client or the >server? The <Output Flushed> is SERVER generated. Not client generated. It is technically possible to overflow gbII's buffer, but it would lock up the client since it would be stuck in a read call. The server-client protocol calls for every line to be newline terminated and at present has kept lines to less than 1024 bytes. Except for map/orbit data but the client handles these differently so as to avoid any problems. The server should write() the output to the person's file descriptor instead of putting the <Output Flushed>. I've just never taken the time to fix this. >
Technical Details
Message-ID:
<1hubk8INNh94@pith.uoregon.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!usenet.coe.montana.edu!news.uoregon.edu!darkwing.uoregon.edu!kofflevaReferences:
<23129@venera.isi.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!usenet.coe.montana.edu!news.uoregon.edu!darkwing.uoregon.edu!koffleva From: koffleva@darkwing.uoregon.edu (A Ghost Walking in the Shadows) Newsgroups: alt.games.gb Subject: Re: tac command Date: 31 Dec 1992 08:39:36 GMT Organization: University of Oregon Network Services Lines: 22 Distribution: alt Message-ID: <1hubk8INNh94@pith.uoregon.edu> References: <23129@venera.isi.edu> NNTP-Posting-Host: darkwing.uoregon.edu