From daviesalex at gmail.com Tue Feb 7 09:25:47 2006 From: daviesalex at gmail.com (Alex Davies) Date: Tue, 7 Feb 2006 09:25:47 +0000 Subject: Tux listen on different IP or Port Message-ID: <379f2ead0602070125r1afc87a6q@mail.gmail.com> Hi, I want to use Tux as well as apache on one server and was wondeirng how I can do this under RHEL4. I can't find a "listen" or "bind" option in /etc/sysconfig/tux. Any pointers would be greatly appreciated. At the moment it seems to be binding to all IPs on port 80. Many thanks, Alex Davies -------------- next part -------------- An HTML attachment was scrubbed... URL: From mayuran.yogarajah at casalemedia.com Tue Feb 7 17:33:04 2006 From: mayuran.yogarajah at casalemedia.com (Mayuran Yogarajah) Date: Tue, 07 Feb 2006 12:33:04 -0500 Subject: Tux listen on different IP or Port In-Reply-To: <379f2ead0602070125r1afc87a6q@mail.gmail.com> References: <379f2ead0602070125r1afc87a6q@mail.gmail.com> Message-ID: <43E8D9D0.6050302@casalemedia.com> You can change the port by altering the file /proc/net/tux/0/listen/0 M Alex Davies wrote: > Hi, > > I want to use Tux as well as apache on one server and was wondeirng > how I can do this under RHEL4. > > I can't find a "listen" or "bind" option in /etc/sysconfig/tux. > > Any pointers would be greatly appreciated. At the moment it seems to > be binding to all IPs on port 80. > > Many thanks, > > Alex Davies > >------------------------------------------------------------------------ > >_______________________________________________ >tux-list mailing list >tux-list at redhat.com >https://www.redhat.com/mailman/listinfo/tux-list > From daviesalex at gmail.com Wed Feb 8 14:24:21 2006 From: daviesalex at gmail.com (Alex Davies) Date: Wed, 8 Feb 2006 14:24:21 +0000 Subject: Tux listen on different IP or Port In-Reply-To: <43E8D9D0.6050302@casalemedia.com> References: <379f2ead0602070125r1afc87a6q@mail.gmail.com> <43E8D9D0.6050302@casalemedia.com> Message-ID: <379f2ead0602080624o299632aar@mail.gmail.com> Hi, Many thanks for this - it looks great except I can't actually edit that file :) How do you suggest I change it? I just cant get it to listen on 8080 with "clientport" in /etc/sysconfig/tux! Many thanks, Alex On 07/02/06, Mayuran Yogarajah wrote: > You can change the port by altering the file > > /proc/net/tux/0/listen/0 > > M > > Alex Davies wrote: > > > Hi, > > > > I want to use Tux as well as apache on one server and was wondeirng > > how I can do this under RHEL4. > > > > I can't find a "listen" or "bind" option in /etc/sysconfig/tux. > > > > Any pointers would be greatly appreciated. At the moment it seems to > > be binding to all IPs on port 80. > > > > Many thanks, > > > > Alex Davies > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > >tux-list mailing list > >tux-list at redhat.com > >https://www.redhat.com/mailman/listinfo/tux-list > > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > -- Alex Davies // http://www.davz.net This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately by e-mail and delete this e-mail permanently. Contact me - MSN: a_davs at hotmail.com SKYPE: alex.davies From max at expires-2004.workforce.de Wed Feb 8 15:29:25 2006 From: max at expires-2004.workforce.de (Max Helmet) Date: Wed, 8 Feb 2006 16:29:25 +0100 Subject: AW: Tux listen on different IP or Port In-Reply-To: <379f2ead0602080624o299632aar@mail.gmail.com> Message-ID: Hi Alex, If you want to use Apache and TUX on the same machine, you usually configure Apache to listen on port 8080 and TUX to forward requests to that port by adding the following line to /etc/sysctl.tux (create it, if it doesn't exists): net.tux.clientport = 8080 clientport is the port on which Apache will listen. There used to be a serverport parameter which controlled the port on which TUX would listen, however that has changed to /proc/net/tux/0/listen/0 in TUX 2.0. Unfortuntely, as a result you can't configure that setting neither via /etc/sysconfig/tux nor /etc/sysctl.tux anymore. Thus, if you want to swap the ports and configure TUX to listen on 8080 and forward requests to Apache listening on port 80, you would have to manually enter the following statement on the command prompt each time the system has booted: echo "http://0.0.0.0:8080" > /proc/net/tux/0/listen/0 Of course you can also add this statement to /etc/rc.d/init.d/tux for your convenience. Regards, Max > Hi, > > Many thanks for this - it looks great except I can't actually > edit that file :) > > How do you suggest I change it? > > I just cant get it to listen on 8080 with "clientport" in > /etc/sysconfig/tux! > > Many thanks, > > Alex > > On 07/02/06, Mayuran Yogarajah wrote: > > You can change the port by altering the file > > > > /proc/net/tux/0/listen/0 > > > > M > > > > Alex Davies wrote: > > > > > Hi, > > > > > > I want to use Tux as well as apache on one server and was wondeirng > > > how I can do this under RHEL4. > > > > > > I can't find a "listen" or "bind" option in /etc/sysconfig/tux. > > > > > > Any pointers would be greatly appreciated. At the moment it seems to > > > be binding to all IPs on port 80. > > > > > > Many thanks, > > > > > > Alex Davies > > > > > > >------------------------------------------------------------------------ > > > > > >_______________________________________________ > > >tux-list mailing list > > >tux-list at redhat.com > > >https://www.redhat.com/mailman/listinfo/tux-list > > > > > > > _______________________________________________ > > tux-list mailing list > > tux-list at redhat.com > > https://www.redhat.com/mailman/listinfo/tux-list > > > > > -- > Alex Davies // http://www.davz.net > > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the sender immediately by e-mail and delete this e-mail permanently. > > Contact me - MSN: a_davs at hotmail.com SKYPE: alex.davies > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > From daviesalex at gmail.com Wed Feb 8 15:56:50 2006 From: daviesalex at gmail.com (Alex Davies) Date: Wed, 8 Feb 2006 15:56:50 +0000 Subject: Tux listen on different IP or Port In-Reply-To: References: <379f2ead0602080624o299632aar@mail.gmail.com> Message-ID: <379f2ead0602080756h2b2fcd2p@mail.gmail.com> Dear Max, I want to run Tux on one IP to serve up soley static content (images and so on). I am under the impression that this will give me greater performance than thttpd. I want to run Apache on another IP to server up PHP websites. echo "http://x.x.x.x:80" > /proc/net/tux/0/listen/0 Indeed changes that file, but when I restart tux it is still listening on all IP addresses bound to that server! If I change the port it just ignores it and remains bound to port 80. With many thanks, Alex On 08/02/06, Max Helmet wrote: > Hi Alex, > > If you want to use Apache and TUX on the same machine, you usually configure > Apache to listen on port 8080 and TUX to forward requests to that port by > adding the following line to /etc/sysctl.tux (create it, if it doesn't > exists): > net.tux.clientport = 8080 > > clientport is the port on which Apache will listen. There used to be a > serverport parameter which controlled the port on which TUX would listen, > however that has changed to /proc/net/tux/0/listen/0 in TUX 2.0. > Unfortuntely, as a result you can't configure that setting neither via > /etc/sysconfig/tux nor /etc/sysctl.tux anymore. > > Thus, if you want to swap the ports and configure TUX to listen on 8080 and > forward requests to Apache listening on port 80, you would have to manually > enter the following statement on the command prompt each time the system has > booted: > echo "http://0.0.0.0:8080" > /proc/net/tux/0/listen/0 > Of course you can also add this statement to /etc/rc.d/init.d/tux for your > convenience. > > Regards, > Max > > > > Hi, > > > > Many thanks for this - it looks great except I can't actually > > edit that file :) > > > > How do you suggest I change it? > > > > I just cant get it to listen on 8080 with "clientport" in > > /etc/sysconfig/tux! > > > > Many thanks, > > > > Alex > > > > On 07/02/06, Mayuran Yogarajah wrote: > > > You can change the port by altering the file > > > > > > /proc/net/tux/0/listen/0 > > > > > > M > > > > > > Alex Davies wrote: > > > > > > > Hi, > > > > > > > > I want to use Tux as well as apache on one server and was wondeirng > > > > how I can do this under RHEL4. > > > > > > > > I can't find a "listen" or "bind" option in /etc/sysconfig/tux. > > > > > > > > Any pointers would be greatly appreciated. At the moment it seems to > > > > be binding to all IPs on port 80. > > > > > > > > Many thanks, > > > > > > > > Alex Davies > > > > > > > > > >------------------------------------------------------------------------ > > > > > > > >_______________________________________________ > > > >tux-list mailing list > > > >tux-list at redhat.com > > > >https://www.redhat.com/mailman/listinfo/tux-list > > > > > > > > > > _______________________________________________ > > > tux-list mailing list > > > tux-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/tux-list > > > > > > > > > -- > > Alex Davies // http://www.davz.net > > > > This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom they > > are addressed. If you have received this email in error please notify > > the sender immediately by e-mail and delete this e-mail permanently. > > > > Contact me - MSN: a_davs at hotmail.com SKYPE: alex.davies > > > > _______________________________________________ > > tux-list mailing list > > tux-list at redhat.com > > https://www.redhat.com/mailman/listinfo/tux-list > > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > -- Alex Davies // http://www.davz.net This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately by e-mail and delete this e-mail permanently. Contact me - MSN: a_davs at hotmail.com SKYPE: alex.davies From max at expires-2004.workforce.de Wed Feb 8 16:17:10 2006 From: max at expires-2004.workforce.de (Max Helmet) Date: Wed, 8 Feb 2006 17:17:10 +0100 Subject: Tux listen on different IP or Port In-Reply-To: <379f2ead0602080756h2b2fcd2p@mail.gmail.com> Message-ID: Hi Alex, You probably altered /proc/net/tux/0/listen/0 while TUX was running. I think TUX needs to be stopped when you alter the file. I just tried the following, and it worked on my end: $ /etc/init.d/tux stop $ echo "http://192.168.0.198:8080" > /proc/net/tux/0/listen/0 $ /etc/init.d/tux start $ netstat -lt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 192.168.0.198:webcache *:* LISTEN Regards, Maximilian > Dear Max, > > I want to run Tux on one IP to serve up soley static content (images > and so on). I am under the impression that this will give me greater > performance than thttpd. > > I want to run Apache on another IP to server up PHP websites. > > echo "http://x.x.x.x:80" > /proc/net/tux/0/listen/0 > > Indeed changes that file, but when I restart tux it is still listening > on all IP addresses bound to that server! > > If I change the port it just ignores it and remains bound to port 80. > > With many thanks, > > Alex From mcd at daviesinc.com Wed Feb 8 16:21:29 2006 From: mcd at daviesinc.com (Chris Davies) Date: Wed, 08 Feb 2006 11:21:29 -0500 Subject: Tux listen on different IP or Port In-Reply-To: References: Message-ID: <43EA1A89.1080607@daviesinc.com> bear in mind that SMP/SMT will have listeners on /proc/net/tux/1, etc depending on the number of cpus Max Helmet wrote: > Hi Alex, > > You probably altered /proc/net/tux/0/listen/0 while TUX was running. I think > TUX needs to be stopped when you alter the file. > > I just tried the following, and it worked on my end: > > $ /etc/init.d/tux stop > $ echo "http://192.168.0.198:8080" > /proc/net/tux/0/listen/0 > $ /etc/init.d/tux start > $ netstat -lt > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 192.168.0.198:webcache *:* LISTEN > > Regards, > Maximilian > > >>Dear Max, >> >>I want to run Tux on one IP to serve up soley static content (images >>and so on). I am under the impression that this will give me greater >>performance than thttpd. >> >>I want to run Apache on another IP to server up PHP websites. >> >>echo "http://x.x.x.x:80" > /proc/net/tux/0/listen/0 >> >>Indeed changes that file, but when I restart tux it is still listening >>on all IP addresses bound to that server! >> >>If I change the port it just ignores it and remains bound to port 80. >> >>With many thanks, >> >>Alex > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > > !DSPAM:43ea1a04219593045745281! > From daviesalex at gmail.com Wed Feb 8 16:25:07 2006 From: daviesalex at gmail.com (Alex Davies) Date: Wed, 8 Feb 2006 16:25:07 +0000 Subject: Tux listen on different IP or Port In-Reply-To: References: <379f2ead0602080756h2b2fcd2p@mail.gmail.com> Message-ID: <379f2ead0602080825o54dc60efv@mail.gmail.com> Dear Max, Many thanks for your help. I don't get the same effect - now it just does not bind to *any* IP and does not produce any logs: [root at trust1 log]# service tux stop Stopping tux: [root at trust1 log]# ps aux | grep tux root 6617 0.0 0.0 5396 656 pts/0 S+ 16:21 0:00 grep tux [root at trust1 log]# echo "http://83.223.121.93:80" > /proc/net/tux/0/listen/0 [root at trust1 log]# service tux start Starting tux: [ OK ] [root at trust1 log]# lynx http://83.223.121.93:80 Exiting via interrupt: 2 (did not work) [root at trust1 log]# tail /proc/net/tux/0/listen/0 http://83.223.121.93:80 My netstat shows a very different output too: [root at trust1 log]# netstat -lt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 *:835 *:* LISTEN tcp 0 0 *:sunrpc *:* LISTEN tcp 0 0 *:10000 *:* LISTEN tcp 0 0 *:ftp *:* LISTEN tcp 0 0 *:ipp *:* LISTEN tcp 0 0 localhost.localdomain:smtp *:* LISTEN tcp 0 0 *:ssh *:* LISTEN [root at trust1 log]# Many thanks for your continued help on this! Alex On 08/02/06, Max Helmet wrote: > Hi Alex, > > You probably altered /proc/net/tux/0/listen/0 while TUX was running. I think > TUX needs to be stopped when you alter the file. > > I just tried the following, and it worked on my end: > > $ /etc/init.d/tux stop > $ echo "http://192.168.0.198:8080" > /proc/net/tux/0/listen/0 > $ /etc/init.d/tux start > $ netstat -lt > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp 0 0 192.168.0.198:webcache *:* LISTEN > > Regards, > Maximilian > > > Dear Max, > > > > I want to run Tux on one IP to serve up soley static content (images > > and so on). I am under the impression that this will give me greater > > performance than thttpd. > > > > I want to run Apache on another IP to server up PHP websites. > > > > echo "http://x.x.x.x:80" > /proc/net/tux/0/listen/0 > > > > Indeed changes that file, but when I restart tux it is still listening > > on all IP addresses bound to that server! > > > > If I change the port it just ignores it and remains bound to port 80. > > > > With many thanks, > > > > Alex > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > -- Alex Davies // http://www.davz.net This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately by e-mail and delete this e-mail permanently. Contact me - MSN: a_davs at hotmail.com SKYPE: alex.davies -------------- next part -------------- An HTML attachment was scrubbed... URL: From daviesalex at gmail.com Wed Feb 8 16:26:09 2006 From: daviesalex at gmail.com (Alex Davies) Date: Wed, 8 Feb 2006 16:26:09 +0000 Subject: Tux listen on different IP or Port In-Reply-To: <43EA1A89.1080607@daviesinc.com> References: <43EA1A89.1080607@daviesinc.com> Message-ID: <379f2ead0602080826m2596a93an@mail.gmail.com> > bear in mind that SMP/SMT will have listeners on /proc/net/tux/1, etc > depending on the number of cpus Yip, I've checked that. They are all unused (its a single CPU box). Many thanks, Alex > > Max Helmet wrote: > > Hi Alex, > > > > You probably altered /proc/net/tux/0/listen/0 while TUX was running. I think > > TUX needs to be stopped when you alter the file. > > > > I just tried the following, and it worked on my end: > > > > $ /etc/init.d/tux stop > > $ echo "http://192.168.0.198:8080" > /proc/net/tux/0/listen/0 > > $ /etc/init.d/tux start > > $ netstat -lt > > Active Internet connections (only servers) > > Proto Recv-Q Send-Q Local Address Foreign Address State > > tcp 0 0 192.168.0.198:webcache *:* LISTEN > > > > Regards, > > Maximilian > > > > > >>Dear Max, > >> > >>I want to run Tux on one IP to serve up soley static content (images > >>and so on). I am under the impression that this will give me greater > >>performance than thttpd. > >> > >>I want to run Apache on another IP to server up PHP websites. > >> > >>echo "http://x.x.x.x:80" > /proc/net/tux/0/listen/0 > >> > >>Indeed changes that file, but when I restart tux it is still listening > >>on all IP addresses bound to that server! > >> > >>If I change the port it just ignores it and remains bound to port 80. > >> > >>With many thanks, > >> > >>Alex > > > > > > _______________________________________________ > > tux-list mailing list > > tux-list at redhat.com > > https://www.redhat.com/mailman/listinfo/tux-list > > > > !DSPAM:43ea1a04219593045745281! > > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > -- Alex Davies // http://www.davz.net This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately by e-mail and delete this e-mail permanently. Contact me - MSN: a_davs at hotmail.com SKYPE: alex.davies From max at expires-2004.workforce.de Wed Feb 8 16:52:21 2006 From: max at expires-2004.workforce.de (Max Helmet) Date: Wed, 8 Feb 2006 17:52:21 +0100 Subject: Tux listen on different IP or Port In-Reply-To: <379f2ead0602080825o54dc60efv@mail.gmail.com> Message-ID: Hi Alex, Looks as if TUX doesn't start on your machine. Are you sure your kernel has TUX support built in? $ ls /proc/sys/net/tux 404_page ftp_subdocroot max_free_requests ... ftp_login_message max_connect $ lsmod Module Size Used by tux 216752 2 $ ps aux | grep TUX root 18510 0.0 0.3 2140 780 pts/0 S 17:05 0:00 [TUX date] root 18512 0.0 0.3 2164 780 ? S 17:05 0:00 [TUX manager] #-1 18513 0.0 0.3 2164 780 ? S 17:05 0:00 [TUX worker 0] ... #-1 18577 0.0 0.3 2164 780 ? S 17:05 0:00 [TUX worker 0] root 18511 0.0 0.0 0 0 ? SW 17:05 0:00 [TUX logger] root 18623 0.0 0.1 1464 468 pts/0 S 17:22 0:00 grep TUX Please notice the capitals in "grep TUX" Max From daviesalex at gmail.com Wed Feb 8 17:23:04 2006 From: daviesalex at gmail.com (Alex Davies) Date: Wed, 8 Feb 2006 17:23:04 +0000 Subject: Tux listen on different IP or Port In-Reply-To: References: <379f2ead0602080825o54dc60efv@mail.gmail.com> Message-ID: <379f2ead0602080923w197bf28dt@mail.gmail.com> Dear Tristan, Tux runs just fine before the change on BOTH ips that are bound, but when I make the change to get it to sit on just the one it stops working on either... very odd! With best wishes, Alex On 08/02/06, Max Helmet wrote: > Hi Alex, > > Looks as if TUX doesn't start on your machine. Are you sure your kernel has > TUX support built in? > $ ls /proc/sys/net/tux > 404_page ftp_subdocroot max_free_requests > ... > ftp_login_message max_connect > $ lsmod > Module Size Used by > tux 216752 2 > $ ps aux | grep TUX > root 18510 0.0 0.3 2140 780 pts/0 S 17:05 0:00 [TUX date] > root 18512 0.0 0.3 2164 780 ? S 17:05 0:00 [TUX manager] > #-1 18513 0.0 0.3 2164 780 ? S 17:05 0:00 [TUX worker > 0] > ... > #-1 18577 0.0 0.3 2164 780 ? S 17:05 0:00 [TUX worker > 0] > root 18511 0.0 0.0 0 0 ? SW 17:05 0:00 [TUX logger] > root 18623 0.0 0.1 1464 468 pts/0 S 17:22 0:00 grep TUX > > Please notice the capitals in "grep TUX" > > Max > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > -- Alex Davies // http://www.davz.net This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately by e-mail and delete this e-mail permanently. Contact me - MSN: a_davs at hotmail.com SKYPE: alex.davies From max at expires-2004.workforce.de Fri Feb 10 08:30:53 2006 From: max at expires-2004.workforce.de (Max Helmet) Date: Fri, 10 Feb 2006 09:30:53 +0100 Subject: Tux listen on different IP or Port In-Reply-To: <379f2ead0602080923w197bf28dt@mail.gmail.com> Message-ID: Hi Alex, I'm not sure what causes your problem, however you could work around this with iptables: $ iptables -t nat -A PREROUTING -i eth0 -p tcp -d ! 83.223.121.93 --dport 80 -j REDIRECT --to-port 8080 This should redirect all incoming requests on port 80 to Apache running on 8080, except for the IP address 83.223.121.93 where they would get served by TUX. Quick and dirty, I know, but at least you get started with the fastest webserver around. Regards, Max Reference: http://www.netfilter.org/documentation/HOWTO//NAT-HOWTO-6.html#ss6.2 > -----Urspr?ngliche Nachricht----- > Von: tux-list-bounces at redhat.com [mailto:tux-list-bounces at redhat.com]Im > Auftrag von Alex Davies > Gesendet: Mittwoch, 8. Februar 2006 18:23 > An: TUX discussion list > Betreff: Re: Tux listen on different IP or Port > > > Dear Tristan, > > Tux runs just fine before the change on BOTH ips that are bound, but > when I make the change to get it to sit on just the one it stops > working on either... very odd! > > With best wishes, > > Alex > > On 08/02/06, Max Helmet wrote: > > Hi Alex, > > > > Looks as if TUX doesn't start on your machine. Are you sure > your kernel has > > TUX support built in? > > $ ls /proc/sys/net/tux > > 404_page ftp_subdocroot max_free_requests > > ... > > ftp_login_message max_connect > > $ lsmod > > Module Size Used by > > tux 216752 2 > > $ ps aux | grep TUX > > root 18510 0.0 0.3 2140 780 pts/0 S 17:05 0:00 > [TUX date] > > root 18512 0.0 0.3 2164 780 ? S 17:05 0:00 > [TUX manager] > > #-1 18513 0.0 0.3 2164 780 ? S 17:05 0:00 > [TUX worker > > 0] > > ... > > #-1 18577 0.0 0.3 2164 780 ? S 17:05 0:00 > [TUX worker > > 0] > > root 18511 0.0 0.0 0 0 ? SW 17:05 0:00 > [TUX logger] > > root 18623 0.0 0.1 1464 468 pts/0 S 17:22 0:00 grep TUX > > > > Please notice the capitals in "grep TUX" > > > > Max > > > > _______________________________________________ > > tux-list mailing list > > tux-list at redhat.com > > https://www.redhat.com/mailman/listinfo/tux-list > > > > > -- > Alex Davies // http://www.davz.net > > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the sender immediately by e-mail and delete this e-mail permanently. > > Contact me - MSN: a_davs at hotmail.com SKYPE: alex.davies > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > From lisbon2006 at gmail.com Thu Feb 16 09:24:47 2006 From: lisbon2006 at gmail.com (X X) Date: Thu, 16 Feb 2006 09:24:47 +0000 Subject: Perserving longer time static pages onc caches? Message-ID: <14e4f1e00602160124u62861252l780eff155c2c25ce@mail.gmail.com> Hi I'm using tux and apache on same server. Tux serves static pages and dynamic ones are redirect/served by apache how may I tell to all cache systems between client and tux/apache servers that those static pages should remain valid for longer periods? If I edit /etc/tux.mime.types and for example change image/gif gif | 3600 to image/gif gif | 7200 would it tell caches that documents of type gif will remain valid for 2hours instead of only 1 hour? Would it benecessary to change something on apache (1.3) config file? I guess it won't be needed as it will only serve redirected requests from tux for dynamic contents. thanks Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolas at incrowd.be Thu Feb 16 17:45:18 2006 From: nicolas at incrowd.be (Nicolas Van Eenaeme) Date: Thu, 16 Feb 2006 18:45:18 +0100 Subject: Where did it go? Message-ID: <20060216174517.D2849386A0@asia.telenet-ops.be> Hi all, I've a new server and I want to install TUX but the sourcecode is gone? http://people.redhat.com/~mingo/TUX-patches/ And the patches for the 2.4 kernel are also gone? Where can I find the sourcecode? I don't want the binary RPM because I'm using Debian instead of RedHat. Thanks in advance! Nicolas Van Eenaeme From nicolas at incrowd.be Thu Feb 16 22:06:53 2006 From: nicolas at incrowd.be (Nicolas Van Eenaeme) Date: Thu, 16 Feb 2006 23:06:53 +0100 Subject: Tux crashed Message-ID: <20060216220654.1B4393827A@hoboe2bl1.telenet-ops.be> Hi all, Tux just crashed: Feb 16 20:36:19 static4 kernel: PGD 102c1c067 PUD 102c1d067 PMD 0 Feb 16 20:36:19 static4 kernel: CPU 0 Feb 16 20:36:19 static4 kernel: Modules linked in: i2c_amd756 hw_random i2c_amd8111 i2c_core generic ide_core psmouse genrtc unix Feb 16 20:36:19 static4 kernel: Pid: 20428, comm: tux Not tainted 2.6.15.2-tux #1 Feb 16 20:36:19 static4 kernel: RIP: 0010:[] {do_send_abuf+209} Feb 16 20:36:19 static4 kernel: RSP: 0018:ffff810102ef7e88 EFLAGS: 00010246 Feb 16 20:36:19 static4 kernel: RAX: 0000000000000000 RBX: ffffffff805a09c0 RCX: ffff81011eaa1560 Feb 16 20:36:19 static4 kernel: RDX: 00000000ffffff98 RSI: 0000000000000000 RDI: ffff8100de29e0c0 Feb 16 20:36:19 static4 kernel: RBP: ffff81011ef22000 R08: 0000000000004040 R09: 0000000000000000 Feb 16 20:36:19 static4 kernel: R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000 Feb 16 20:36:19 static4 kernel: R13: ffffffff805a0cc8 R14: ffff810102ef7ee8 R15: 0000000000000000 Feb 16 20:36:19 static4 kernel: FS: 00002aaaab191700(0000) GS:ffffffff805ac800(0000) knlGS:0000000000000000 Feb 16 20:36:19 static4 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Feb 16 20:36:19 static4 kernel: CR2: 0000000000000038 CR3: 0000000102d3b000 CR4: 00000000000006e0 Feb 16 20:36:19 static4 kernel: Process tux (pid: 20428, threadinfo ffff810102ef6000, task ffff81011eaa1560) Feb 16 20:36:19 static4 kernel: Stack: ffffffff805a09c0 0000000000000004 ffffffff805a0cd0 ffffffff803e0213 Feb 16 20:36:19 static4 kernel: 00000001805a0cc8 ffffffff803e1251 ffffffff805a09c0 ffffffff805a0cd0 Feb 16 20:36:19 static4 kernel: ffffffff805a09c0 00007fffffad6cf0 Feb 16 20:36:19 static4 kernel: Call Trace:{tux_schedule_atom+19} {process_requests+161} Feb 16 20:36:19 static4 kernel: {event_loop+148} {__sys_tux+710} Feb 16 20:36:19 static4 kernel: {error_exit+0} {system_call+126} Feb 16 20:36:19 static4 kernel: Feb 16 20:36:19 static4 kernel: Feb 16 20:36:19 static4 kernel: Code: 48 c7 40 38 00 00 00 00 48 8b bd 08 02 00 00 e8 2b dd d6 ff Feb 16 20:36:19 static4 kernel: <5>TUX: thread 0 stopping ... My kernel version is: Linux static4 2.6.15.2-tux #1 SMP Wed Feb 1 08:05:13 CET 2006 x86_64 GNU/Linux Any idea how this happened and more important: how I can prevent this? Thanks a lot! Nicolas Van Eenaeme From mcd at daviesinc.com Fri Feb 17 00:09:48 2006 From: mcd at daviesinc.com (Chris Davies) Date: Thu, 16 Feb 2006 19:09:48 -0500 Subject: Tux crashed In-Reply-To: <20060216220654.1B4393827A@hoboe2bl1.telenet-ops.be> References: <20060216220654.1B4393827A@hoboe2bl1.telenet-ops.be> Message-ID: <43F5144C.4020000@daviesinc.com> I had similar problems with SMP & SMT kernels around Jan 20th with 2.6.15. Try a non-SMP kernel and I think the problem will go away. I got no response to my prior messages posted on the list. Nicolas Van Eenaeme wrote: > Hi all, > > Tux just crashed: > > Feb 16 20:36:19 static4 kernel: PGD 102c1c067 PUD 102c1d067 PMD 0 > Feb 16 20:36:19 static4 kernel: CPU 0 > Feb 16 20:36:19 static4 kernel: Modules linked in: i2c_amd756 hw_random > i2c_amd8111 i2c_core generic ide_core psmouse genrtc unix > Feb 16 20:36:19 static4 kernel: Pid: 20428, comm: tux Not tainted > My kernel version is: > Linux static4 2.6.15.2-tux #1 SMP Wed Feb 1 08:05:13 CET 2006 x86_64 > GNU/Linux From SoNNy at PrisonServer.com Fri Feb 17 17:14:53 2006 From: SoNNy at PrisonServer.com (SoNNy at PrisonServer.com) Date: Fri, 17 Feb 2006 18:14:53 +0100 Subject: Tux crashed In-Reply-To: <43F5144C.4020000@daviesinc.com> References: <20060216220654.1B4393827A@hoboe2bl1.telenet-ops.be> <43F5144C.4020000@daviesinc.com> Message-ID: <43F6048D.3010909@PrisonServer.com> Chris Davies wrote: > I had similar problems with SMP & SMT kernels around Jan 20th with > 2.6.15. > > Try a non-SMP kernel and I think the problem will go away. I got no > response to my prior messages posted on the list. > Yeah, me too. If you want a stable server using TUX, just go away from SMP kernels. Just my experience. Regards, Juan From lisbon2006 at gmail.com Mon Feb 20 14:45:16 2006 From: lisbon2006 at gmail.com (X X) Date: Mon, 20 Feb 2006 14:45:16 +0000 Subject: Tux crashed In-Reply-To: <43F6048D.3010909@PrisonServer.com> References: <20060216220654.1B4393827A@hoboe2bl1.telenet-ops.be> <43F5144C.4020000@daviesinc.com> <43F6048D.3010909@PrisonServer.com> Message-ID: <14e4f1e00602200645i76542b98ib145605515d50d36@mail.gmail.com> Hi does anyone has an idea how to send headers via tux to clients (on a per document or directory basis) with expires dates? so no ICP queries are even needed? We don't have HTML META tags on documents. Validity (seconds) on a per-file type is not a solutions for us. thanks Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From max at expires-2004.workforce.de Mon Feb 20 17:15:06 2006 From: max at expires-2004.workforce.de (Max Helmet) Date: Mon, 20 Feb 2006 18:15:06 +0100 Subject: AW: Tux crashed In-Reply-To: <14e4f1e00602200645i76542b98ib145605515d50d36@mail.gmail.com> Message-ID: Hi, I think you'll have to write a TUX module in order to accomplish this. Regards, Max -----Urspr?ngliche Nachricht----- Von: tux-list-bounces at redhat.com [mailto:tux-list-bounces at redhat.com]Im Auftrag von X X Gesendet: Montag, 20. Februar 2006 15:45 An: TUX discussion list Betreff: Re: Tux crashed Hi does anyone has an idea how to send headers via tux to clients (on a per document or directory basis) with expires dates? so no ICP queries are even needed? We don't have HTML META tags on documents. Validity (seconds) on a per-file type is not a solutions for us. thanks Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcd at daviesinc.com Tue Feb 21 17:25:18 2006 From: mcd at daviesinc.com (Chris Davies) Date: Tue, 21 Feb 2006 12:25:18 -0500 Subject: Tux crashed In-Reply-To: <43F6048D.3010909@PrisonServer.com> References: <20060216220654.1B4393827A@hoboe2bl1.telenet-ops.be> <43F5144C.4020000@daviesinc.com> <43F6048D.3010909@PrisonServer.com> Message-ID: <43FB4CFE.1000609@daviesinc.com> SoNNy at PrisonServer.com wrote: > Chris Davies wrote: > >> I had similar problems with SMP & SMT kernels around Jan 20th with >> 2.6.15. >> >> Try a non-SMP kernel and I think the problem will go away. I got no >> response to my prior messages posted on the list. >> > Yeah, me too. If you want a stable server using TUX, just go away from > SMP kernels. Just my experience. With the improvements in 2.6, I'm actually seeing a lot less benefit to tux over usermode webservers. Perhaps Redhat has drawn the same conclusion and decided that Tux wasn't worth efforts to fix the bug? I had this problem with a much older 2.6 as well, but, never drew the conclusion that it was SMP that was causing the problem, so, its not a new issue. And I certainly cannot believe that we are the only ones wanting to use Tux on SMP machines. So, we're stuck with 2.4 SMP Tux or 2.6 UniProcessor Tux if we want to use Tux. From SoNNy at PrisonServer.com Tue Feb 21 17:50:49 2006 From: SoNNy at PrisonServer.com (SoNNy at PrisonServer.com) Date: Tue, 21 Feb 2006 18:50:49 +0100 Subject: Tux crashed In-Reply-To: <43FB4CFE.1000609@daviesinc.com> References: <20060216220654.1B4393827A@hoboe2bl1.telenet-ops.be> <43F5144C.4020000@daviesinc.com> <43F6048D.3010909@PrisonServer.com> <43FB4CFE.1000609@daviesinc.com> Message-ID: <43FB52F9.4080408@PrisonServer.com> > With the improvements in 2.6, I'm actually seeing a lot less benefit > to tux over usermode webservers. Yes I read that on some place before. > So, we're stuck with 2.4 SMP Tux or 2.6 UniProcessor Tux if we want to > use Tux. Yeah, I didn't remember 2.4 SMP is ok. That's exactly my experience too. No problems with 2.4-SMP, and 2.6 UniProcessor (even a Single Xeon, seen as 2 CPU and the like, works good on production servers of mine). For example, CentOS 4 + TUX on a Dual machine is a no-no. Regards, Juan From lisbon2006 at gmail.com Fri Feb 24 11:08:46 2006 From: lisbon2006 at gmail.com (lisbon_pt) Date: Fri, 24 Feb 2006 11:08:46 +0000 Subject: Tux / apache / squid(?) questions Message-ID: <14e4f1e00602240308j50149bc1w5bd625eee15cb3ea@mail.gmail.com> Hello I have a TUX (?) problem, but I would like to share with this community. browser /cache ----connect---> FRONT END --- possible redirect to BACKENDs (1) (2) In (1), I have TUX and apache 1.3 with same DOCROOT so I guess TUX will really accelerate responses for request which objects are in this DOCROOT. however if objectas are not in (1), there will be redirected to (several) backends (IIS 5.0 - with header expires configured for 9 days). My doubts are (if someone could help - hope I'm not demanding too much): 1. would the answers sent from (2) throught (1) be cached by TUX? (TUX doesn't seem to me a cache, but an accelerator for user-space web-server, as apache) 2. The solution could be: 1. have squid as cache in FRONTEND 2. requests not served by TUX should be redirected to squid 3. squid would contact BACKENDs (redirect) and will cache answers from backend I really would appreciate any help (I know you all have to do but maybe already faced same quesions) kind regards, lisbon_pt From max at expires-2004.workforce.de Fri Feb 24 12:46:59 2006 From: max at expires-2004.workforce.de (Max Helmet) Date: Fri, 24 Feb 2006 13:46:59 +0100 Subject: Tux / apache / squid(?) questions In-Reply-To: <14e4f1e00602240308j50149bc1w5bd625eee15cb3ea@mail.gmail.com> Message-ID: Hi, TUX can only call the other web server on the same server, it has no ability yet to forward or proxy requests to a separate server. Therefore you will have to go for the 2nd solution: Browser --> TUX -> Squid --> IIS. In addition to that, you could mirror the IIS site via httrack to the TUX frontend servers and create cron jobs that regularly update the local copy. This way you could fully leverage the accelleration capabilities of TUX. Regards, Max > I have a TUX (?) problem, but I would like to share with this community. > > browser /cache ----connect---> FRONT END --- possible redirect to BACKENDs > (1) > (2) > > In (1), I have TUX and apache 1.3 with same DOCROOT > so I guess TUX will really accelerate responses for request which > objects are in this DOCROOT. > > however if objectas are not in (1), there will be redirected to (several) > backends (IIS 5.0 - with header expires configured for 9 days). > > My doubts are (if someone could help - hope I'm not demanding too much): > > 1. would the answers sent from (2) throught (1) be cached by TUX? > (TUX doesn't seem to me a cache, but an accelerator for user-space > web-server, as apache) > > 2. The solution could be: > 1. have squid as cache in FRONTEND > 2. requests not served by TUX should be redirected to squid > 3. squid would contact BACKENDs (redirect) and will cache answers > from backend > > I really would appreciate any help (I know you all have to do but > maybe already > faced same quesions) > > kind regards, > lisbon_pt > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > From lisbon2006 at gmail.com Fri Feb 24 15:29:38 2006 From: lisbon2006 at gmail.com (lisbon_pt) Date: Fri, 24 Feb 2006 15:29:38 +0000 Subject: Tux / apache / squid(?) questions In-Reply-To: References: <14e4f1e00602240308j50149bc1w5bd625eee15cb3ea@mail.gmail.com> Message-ID: <14e4f1e00602240729g2ae778b5n9ccc4531c6418a41@mail.gmail.com> Just another question (if I may): If tux calls apache in the same machine (apache1) and this apache redirect the request to an apache web server in another machine (apache2), the answer will be: 1. apache2 --> apache1 --> tux --> client (Does TUX cache apache2 answer?) OR 2. apache2 --> apache1 --> client (NO TUX and no tux caching) Regards, lisbon_pt On 2/24/06, Max Helmet wrote: > Hi, > > TUX can only call the other web server on the same server, it has no ability > yet to forward or proxy requests to a separate server. Therefore you will > have to go for the 2nd solution: Browser --> TUX -> Squid --> IIS. > > In addition to that, you could mirror the IIS site via httrack to the TUX > frontend servers and create cron jobs that regularly update the local copy. > This way you could fully leverage the accelleration capabilities of TUX. > > Regards, > Max > > > I have a TUX (?) problem, but I would like to share with this community. > > > > browser /cache ----connect---> FRONT END --- possible redirect to BACKENDs > > (1) > > (2) > > > > In (1), I have TUX and apache 1.3 with same DOCROOT > > so I guess TUX will really accelerate responses for request which > > objects are in this DOCROOT. > > > > however if objectas are not in (1), there will be redirected to (several) > > backends (IIS 5.0 - with header expires configured for 9 days). > > > > My doubts are (if someone could help - hope I'm not demanding too much): > > > > 1. would the answers sent from (2) throught (1) be cached by TUX? > > (TUX doesn't seem to me a cache, but an accelerator for user-space > > web-server, as apache) > > > > 2. The solution could be: > > 1. have squid as cache in FRONTEND > > 2. requests not served by TUX should be redirected to squid > > 3. squid would contact BACKENDs (redirect) and will cache answers > > from backend > > > > I really would appreciate any help (I know you all have to do but > > maybe already > > faced same quesions) > > > > kind regards, > > lisbon_pt > > > > _______________________________________________ > > tux-list mailing list > > tux-list at redhat.com > > https://www.redhat.com/mailman/listinfo/tux-list > > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list > From max at expires-2004.workforce.de Fri Feb 24 17:49:50 2006 From: max at expires-2004.workforce.de (Max Helmet) Date: Fri, 24 Feb 2006 18:49:50 +0100 Subject: AW: Tux / apache / squid(?) questions In-Reply-To: <14e4f1e00602240729g2ae778b5n9ccc4531c6418a41@mail.gmail.com> Message-ID: Hi, TUX accellerates HTTP by serving static HTML and image files without the overhead of an user/kernel switch and by reducing the request processing to an absolute minimum. It just "peeks" into the incoming request and then decides whether it can serve the response by itself or better leave it as is and hand the job over to the user-space web server. After the hand-over TUX stops dealing with the request, leaving sole responsibility to the web server of choice. In this process, no proxying and no HTTP redirection is involved. This said, TUX will not cache any responses coming from the user-space web server. TUX specializes in serving static files and does extremely well at it - nothing more, nothing less. If your primary concern is reverse proxying, TUX probably isn't right for you. Regards, Max > Just another question (if I may): > > If tux calls apache in the same machine (apache1) and this apache redirect > the request to an apache web server in another machine (apache2), the > answer will be: > > 1. > apache2 --> apache1 --> tux --> client > (Does TUX cache apache2 answer?) > > OR > > 2. apache2 --> apache1 --> client (NO TUX and no tux caching) > > Regards, > lisbon_pt > > > > On 2/24/06, Max Helmet wrote: > > Hi, > > > > TUX can only call the other web server on the same server, it > has no ability > > yet to forward or proxy requests to a separate server. > Therefore you will > > have to go for the 2nd solution: Browser --> TUX -> Squid --> IIS. > > > > In addition to that, you could mirror the IIS site via httrack > to the TUX > > frontend servers and create cron jobs that regularly update the > local copy. > > This way you could fully leverage the accelleration capabilities of TUX. > > > > Regards, > > Max > > > > > I have a TUX (?) problem, but I would like to share with this > community. > > > > > > browser /cache ----connect---> FRONT END --- possible > redirect to BACKENDs > > > (1) > > > (2) > > > > > > In (1), I have TUX and apache 1.3 with same DOCROOT > > > so I guess TUX will really accelerate responses for request which > > > objects are in this DOCROOT. > > > > > > however if objectas are not in (1), there will be redirected > to (several) > > > backends (IIS 5.0 - with header expires configured for 9 days). > > > > > > My doubts are (if someone could help - hope I'm not demanding > too much): > > > > > > 1. would the answers sent from (2) throught (1) be cached by TUX? > > > (TUX doesn't seem to me a cache, but an accelerator for user-space > > > web-server, as apache) > > > > > > 2. The solution could be: > > > 1. have squid as cache in FRONTEND > > > 2. requests not served by TUX should be redirected to squid > > > 3. squid would contact BACKENDs (redirect) and will cache answers > > > from backend > > > > > > I really would appreciate any help (I know you all have to do but > > > maybe already > > > faced same quesions) > > > > > > kind regards, > > > lisbon_pt > > > > > > _______________________________________________ > > > tux-list mailing list > > > tux-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/tux-list > > > > > > > _______________________________________________ > > tux-list mailing list > > tux-list at redhat.com > > https://www.redhat.com/mailman/listinfo/tux-list > > > > _______________________________________________ > tux-list mailing list > tux-list at redhat.com > https://www.redhat.com/mailman/listinfo/tux-list >