Re: [patch] TUX 2.4.2-P3

[Marcus Gruendler <runner tamalin de>]

On Sunday 11 March 2001 16:41 you wrote:
[...]
>
> i suspect Netscape kept a HTTP/1.1 keepalive connection around - just in
> case you enter another request. If this is the case then this is a valid
> optimization - Netscape keeps the TCP connection open, so it doesnt have
> to build it again for the next request.
>
> TUX has a default keepalive timeout of 30 seconds - this is perhaps a bit
> too low. You can change it to eg. 5 minutes:
>
> 	echo 150 > /proc/sys/net/tux/keepalive_timeout
>
[...]

Okay that seems to work here.

But I encounter another problem dealing with modules. Assume I have a file 
/var/www/html/demo.tux and /var/www/tux-modules/demo.tux.so (yes, the *.so's 
in the tux-2.0.x.tar.gz package should compile to demo*.tux.so ;). But in the 
/etc/sysconfig/tux file there are no modules entered.

When I make a request to http://myhost/demo.tux, tux crashes and produces 
this error log:

invalid operand: 0000
CPU:    0
EIP:    0010:[event_loop+384/444]
EFLAGS: 00010246
eax: c221a3c0   ebx: c4798000   ecx: c04e6320   edx: c6b46800
esi: c4798000   edi: c04e6320   ebp: c4799f58   esp: c4799f44
ds: 0018   es: 0018   ss: 0018
Process tux (pid: 836, stackpage=c4799000)
Stack: c04e6320 00000000 ffffffff 00000000 c6b46800 c4799fbc c02307eb c04e6320
       c4798000 00000000 bfffdfac 00000073 00000000 c4798000 4015e820 c04e6328
       40018000 3a88537b 00000000 40018000 00000001 00005401 c04e6320 c6de07c0
Call Trace: [__sys_tux+1783/3812] [sys_ioctl+504/517] [system_call+51/56]

Code: 0f 0b 89 17 c7 06 00 00 00 00 31 c0 eb 22 89 f6 c7 03 00 00 
 Possibly unexpected TUX-thread exit(11) at c010923b?

It seems as tux does not check if there is really a user module loaded. In 
such a case it should at least reply with the content of demo.tux (which is 
empty of course) or (better) with a 404 error.

Bye, Marcus

-- 
Marcus Gruendler
eMail: runner@tamalin.de
WWW: http://www.tamalin.de/runner/index.html