According to [EMAIL PROTECTED]: While burning my CPU.
>
Hello Scott.
> I've been running Linux for a few weeks and doing a lot of reading.
> There are a few questions I can't find answers to. I thought I'd save
> them up and ask a few at once.
>
> * Is there a way to speed up the timing on TCP/IP frames? For example, I
> can watch an SMTP exchange between my system and another host. His
> system sends a frame with a block of text, my system sends an ACK
> frame. If his system misses this ACK, everything stops. I never see my
> system try to send the ACK again. Is there a timer I can fiddle with?
> After a few minutes his system finally sends RST and we have to start
> over again.
Are you talking about IP over AX25, if so yes there is, but its NOT a
recomended thing to do, what you need to do (if you have not done so) is
set the IRTT with the route command.
If the systems just dont communicate properly period, then there is
something else wrong.
Route add <host> mss 256 window 944 irtt 3000 ax0
Now the above sets up the interface with a mtu of 256 (yes it says mss but
it realy is the MTU) use a window of 944 which should allow 2 frames at once
to be sent, and set the initail reutern time to 3 seconds on interface ax0.
You can alter the IP timers in ./linux/net/ipv4/tcp_timer.c and
./linux/net/ipv4/tcp_output.c but that is not recommended.
If the IRTT command does not help, send me a message i will then tell you
how to change the default IP timers.
>
> * Can I delete the "message.log" file from time to time or do I need to
> prune it with some program? Mine is getting close to 2m in size.
Yes you can delete it.
>
> * How can I stop the annoying "mail beep" my speaker emits with each
> incoming mail while I'm in X. I no longer get this while using the
> standard VT after I found how to change the bash shell variables but
> while running fvwm95 I still get a beep. I'm on a few fairly active
> lists and this is getting old :)
Comment out the comsat daemon in /etc/inetd.conf and send the inetd process
a -HUP signal, like explaned at the top of that file.
Put 'biff n' somewhere in one of you enviroment files, for example .bashrc
.profile etc.
>
>
> --
> Scott Felton
> Slackware Linux v3.6
> [EMAIL PROTECTED]
> http://www.k3ir.ampr.org
>
>
--
Regards Richard.
[EMAIL PROTECTED]
