After looking at my 2.2.16 SuSE 7.0 system, youre right. there is no ctc
directory in /proc/net. Then I looked at a SuSE 7.0 system which has been
upgraded to a 2.2.19 kernel and the files are there. I built the 2.2.19
kernel from kernel.org source + all 2.2.19 developerworks patches. So - it
looks like your doc is for a higher level 2.2 system what what comes with
SuSE 7.0 . A quick grep of the source on the 2.2.16 system does not reveal
a buffersize variable, and it looks like it's not really configurable like
that anyway.
I went to the 2.2.19 kernel to get a tape driver. As a bonus, the CTC
connection seems faster and more stable as well.
So - I guess the answer your question is: "There is no such adjustment on
2.2.16" If you are happy with the current function of your CTC, then I
think you're done. Otherwise, the upgrade to 2.2.19 is pretty painless.
There are lots of kernel upgrade HOWTOs out there (linux.org) and the list
will be more than willing to help.
Jay Brenneman
"Scully, William"
<WILLIAM.SCULLY@c To: [EMAIL PROTECTED]
a.com> cc:
Sent by: Linux on Subject: Re: Buffersize on Linux CTC
Driver
390 Port
<[EMAIL PROTECTED]
IST.EDU>
02/14/02 09:49 PM
Please respond to
Linux on 390 Port
Jay,
A CTC is used to connect Linux to TCP/IP on VM. Since that's the only way
I
can gain access (Telnet) to the Linux server via TCP/IP, I'm as sure as I
can be that the CTC driver -is- loaded. I'm also certain that the named
file and directories do not exist.
linux016:~ # lsmod
Module Size Used by
ctc 21220 1 (autoclean)
linux016:~ # cd /proc
linux016:/proc # cd net
linux016:/proc/net # ls
. dev igmp ip_mr_cache netstat rpc sockstat udp
.. dev_mcast ip_fwchains ip_mr_vif raw rt_cache tcp unix
arp dev_stat ip_fwnames netlink route snmp tr_rif
linux016:/proc/net #
I'll mention that I'm at the 2.2.16 level of SuSE 7.0 GA. Are you seeing
different results with your system? If so, what distribution are you
using?
I personally haven't yet worked with the 2.4 kernel and if the CTC driver
works differently at that level, I'd like to hear that. I'll mention again
that the quote from the manual was for the 2.2.16 level of code. Again,
perhaps, we've missed some service?
Thanks for your comments. The more I check the more I learn about all this
stuff! ;-)
-----Original Message-----
From: Robert J Brenneman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 3:34 PM
To: [EMAIL PROTECTED]
Subject: Re: Buffersize on Linux CTC Driver
The file is not there because the driver is not yet loaded. You have to
load the driver first before you can change the buffersize. All the
appropriate /proc stuff gets created after the driver loads.
Jay Brenneman
"Scully, William"
<WILLIAM.SCULLY@c To:
[EMAIL PROTECTED]
a.com> cc:
Sent by: Linux on Subject: Buffersize on
Linux
CTC Driver
390 Port
<[EMAIL PROTECTED]
IST.EDU>
02/14/02 02:26 PM
Please respond to
Linux on 390 Port
The IBM "Linux for S/390 Device Drivers and Installation Commands"
document, dated 18 July 2001, in Chapter Seven, "Linux for S/390 CTC/ESCON
Device Driver", has Usage Note 2 under "Preparing the Connection" which
reads:
Definitions on the remote side
Set up the TCP/IP on the remote side, as described in the reference
manuals.
This will vary depending on which operating system is used on the remote
side.
Note: It is important that you have IOBUFFERSIZE 32678 defined because
the
LINUX for S/390 CTC driver works with 32k internally. This is
configurable
for each device by writing the value to the buffersize file for that
device
(proc/net/ctc/<devicename>/buffersize ), for example
echo 32768 >/proc/net/ctc/ctc0/buffersize
I'm not sure how this is accomplished. Logging on as root and issuing the
command doesn't work. Here's what I get:
LINUXWPS:/proc # echo 32768 >/proc/net/ctc/ctc0/buffersize
bash: /proc/net/ctc/ctc0/buffersize: No such file or directory
What is the correct technique for creating the appropriate directories and
file?
William P. Scully
Systems Programmer
Computer Associates International, Inc
[EMAIL PROTECTED]
