[1925] in SIPB-AFS-requests
Re: running /usr/local/etc/elcsd on charon,rtfm,rosebud,ronald-ann
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Fri Apr 7 15:45:19 1995
To: mhpower@MIT.EDU
Cc: jweiss@MIT.EDU, charon-maintainers@MIT.EDU, rtfm-maintainers@MIT.EDU,
sipb-afsreq@MIT.EDU
In-Reply-To: "[1922] in SIPB-AFS-requests",
"[1232] in Charon_Maintainers_Archive",
"[3784] in RTFM_Maintainers_Archive"
Date: Fri, 07 Apr 1995 15:43:23 EDT
From: Jonathon Weiss <jweiss@MIT.EDU>
>> As far as I can tell, the elcsd in Ultrix 4.3 and 4.4 still accepts
>> tcp connections on port 704 regardless of whether LOGREM is set in
>> /etc/elcsd.conf (which I seem to have written as /etc/elscd.conf in my
I believe that this is true.
>> script). Given that we'd be running a version of elcsd different from
>> the standard release anyway, I'd prefer to stay with the version I
>> built. For example, unless someone has read the 4.3 source code, we
>> really don't know if sending some particular data to port 704 might
>> again trigger the cpu-time problem or some other problem...
I've looked at the code at least a little, I'm pretty sure that I'm
not supposed to show it to people, because it is under an ultrix
source licence. But from my quick look at it (and talking to Ezra) I
do believe that the bug is fixed. I don't think it is especially
important, but I wonder if your binary will DTRT (or at least do
whatever the standard binary does) if it is dynamically reconfigured
to accept remote connections when it was not initially configured to
do so. The reason I don't think it's especially important is that I
don't think it's anything we're likely to do. Despite this, I don't
have a problem with our continuing to run your version.
Jonathon
