bwm-tools-tech Mailing List for Bandwidth Management Tools (Page 2)
Brought to you by:
nkukard
Menu
▾
▴
bwm-tools-tech — General & Technical Discussion
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(13) |
Jul
(2) |
Aug
(1) |
Sep
(5) |
Oct
(10) |
Nov
(11) |
Dec
(8) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(6) |
Feb
(3) |
Mar
(22) |
Apr
(26) |
May
(15) |
Jun
|
Jul
(8) |
Aug
(2) |
Sep
(3) |
Oct
(4) |
Nov
|
Dec
(1) |
| 2005 |
Jan
(2) |
Feb
(6) |
Mar
(12) |
Apr
(34) |
May
(23) |
Jun
(21) |
Jul
|
Aug
(4) |
Sep
(5) |
Oct
(3) |
Nov
(2) |
Dec
|
| 2006 |
Jan
(3) |
Feb
(28) |
Mar
(12) |
Apr
(6) |
May
(17) |
Jun
(5) |
Jul
(19) |
Aug
(15) |
Sep
(10) |
Oct
(12) |
Nov
(1) |
Dec
|
| 2007 |
Jan
(5) |
Feb
(1) |
Mar
(5) |
Apr
(5) |
May
(7) |
Jun
(6) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(5) |
Jun
|
Jul
|
Aug
(8) |
Sep
(8) |
Oct
(2) |
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(7) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Nigel K. <nk...@lb...> - 2008-09-15 05:26:29
|
> I got error on make, need advise from all. > > Thank you > > Error logs > > s01:/opt/bwm_tools-0.3.0 # make > make all-recursive > make[1]: Entering directory `/opt/bwm_tools-0.3.0' > Making all in lib > make[2]: Entering directory `/opt/bwm_tools-0.3.0/lib' > /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I. ./include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/ include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -M D -MP -MF .deps/libbwm_la-xmlConf.Tpo -c -o libbwm_la-xmlConf.lo `test -f 'xmlCo nf.c' || echo './'`xmlConf.c > gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/u sr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g - O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.o > In file included from ../include/flow.h:30, > from ../include/autoclass.h:29, > from xmlConf.c:32: > /usr/include/linux/netfilter.h:40: error: expected specifier-qualifier-list befo re â__u32â > make[2]: *** [libbwm_la-xmlConf.lo] Error 1 > make[2]: Leaving directory `/opt/bwm_tools-0.3.0/lib' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/opt/bwm_tools-0.3.0' > make: *** [all] Error 2 Please try the attached patch and let me know if it fixes your problem. Regards Nigel |
|
From: Alvin A. <alv...@ya...> - 2008-09-13 22:41:08
|
Hi all,
I got error on make, need advise from all.
Thank you
Error logs
s01:/opt/bwm_tools-0.3.0 # make
make all-recursive
make[1]: Entering directory `/opt/bwm_tools-0.3.0'
Making all in lib
make[2]: Entering directory `/opt/bwm_tools-0.3.0/lib'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I. ./include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/ include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -M D -MP -MF .deps/libbwm_la-xmlConf.Tpo -c -o libbwm_la-xmlConf.lo `test -f 'xmlCo nf.c' || echo './'`xmlConf.c
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/u sr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g - O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.o
In file included from ../include/flow.h:30,
from ../include/autoclass.h:29,
from xmlConf.c:32:
/usr/include/linux/netfilter.h:40: error: expected specifier-qualifier-list befo re â__u32â
make[2]: *** [libbwm_la-xmlConf.lo] Error 1
make[2]: Leaving directory `/opt/bwm_tools-0.3.0/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/bwm_tools-0.3.0'
make: *** [all] Error 2
|
|
From: Nigel K. <nk...@lb...> - 2008-09-08 18:43:08
|
Hi > here any good news. > > Your bwm_tools works fine ! > The problem, that bwmd crash every day, was a defect RAM on the Motherboard ! > > On Friday i put the new RAM in the Server and now bwmd work very fine. :) > Thanks for your time. Pleasure :) -N |
|
From: <lie...@we...> - 2008-09-08 18:39:31
|
Hi Nigel, here any good news. Your bwm_tools works fine ! The problem, that bwmd crash every day, was a defect RAM on the Motherboard ! On Friday i put the new RAM in the Server and now bwmd work very fine. Thanks for your time. I now i will try the installation from bwm_tools on Fedora 9 in the next days. I had no time the last week. sorry. Best Regards Ralph > -----Ursprüngliche Nachricht----- > Von: "Nigel Kukard" <nk...@lb...> > Gesendet: 02.09.08 14:29:07 > An: Bandwidth Management Tools General & Technical Discussions <bwm...@li...> > Betreff: Re: [bwm-tools-tech] bwmd crash 3-4 times the day > > > I tell you my steps ... > > > > 1. you sent me the file "include/flow.h" > > 2. i open it with an editor, so i see, that you insert a new line (green) > > 3. now i copy this line in the flow.h and saved it > > 4. then i start the installation, and so i sent you the score. > > > > is there any wrong ? > > did you "make clean" between 3 & 4? > > -N > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > bwm-tools-tech mailing list > bwm...@li... > https://lists.sourceforge.net/lists/listinfo/bwm-tools-tech > ______________________________________________________________ "Hostage" mit Bruce Willis kostenlos anschauen! Exklusiv für alle WEB.DE Nutzer. http://www.blockbuster.web.de |
|
From: Nigel K. <nk...@lb...> - 2008-09-02 12:28:49
|
> I tell you my steps ... > > 1. you sent me the file "include/flow.h" > 2. i open it with an editor, so i see, that you insert a new line (green) > 3. now i copy this line in the flow.h and saved it > 4. then i start the installation, and so i sent you the score. > > is there any wrong ? did you "make clean" between 3 & 4? -N |
|
From: <lie...@we...> - 2008-09-01 21:33:45
|
Hi Nigel, i hope so. I tell you my steps ... 1. you sent me the file "include/flow.h" 2. i open it with an editor, so i see, that you insert a new line (green) 3. now i copy this line in the flow.h and saved it 4. then i start the installation, and so i sent you the score. is there any wrong ? regards Ralph > -----Ursprüngliche Nachricht----- > Von: "Nigel Kukard" <nk...@lb...> > Gesendet: 01.09.08 12:22:31 > An: Bandwidth Management Tools General & Technical Discussions <bwm...@li...> > Betreff: Re: [bwm-tools-tech] bwmd crash 3-4 times the day > Hi, > > > this evening i test the installation from bwm_tools-0.3.0 under Fedora 9. > > (Sorry that i make it not faster, but i have no time the last 14 days) > > OK, I change the flow.h file after your instruction. > > Than ..... > > 1. ./configure --> no Problem > > 2. make --> the follow message ... > > > > make > > make all-recursive > > make[1]: Entering directory `/home/Ralph/bwmd/bwm_tools-0.3.0' > > Making all in lib > > make[2]: Entering directory `/home/Ralph/bwmd/bwm_tools-0.3.0/lib' > > /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c -o libbwm_la-xmlConf.lo `test -f 'xmlConf.c' || echo './'`xmlConf.c > > gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.o > > In file included from ../include/flow.h:32, > > from ../include/autoclass.h:30, > > from xmlConf.c:33: > > /usr/include/linux/netfilter.h:40: error: expected specifier-qualifier-list before '__u32' > > make[2]: *** [libbwm_la-xmlConf.lo] Fehler 1 > > make[2]: Leaving directory `/home/Ralph/bwmd/bwm_tools-0.3.0/lib' > > make[1]: *** [all-recursive] Fehler 1 > > make[1]: Leaving directory `/home/Ralph/bwmd/bwm_tools-0.3.0' > > make: *** [all] Fehler 2 > > > > Hope it will help that you find the problem ;-) > > > > I will try to check my second problem this week. > > Than i send you the backtrace. > > Sure you applied the patch I sent to the list? > > -N > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > bwm-tools-tech mailing list > bwm...@li... > https://lists.sourceforge.net/lists/listinfo/bwm-tools-tech > _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 |
|
From: Nigel K. <nk...@lb...> - 2008-09-01 10:22:07
|
Hi, > this evening i test the installation from bwm_tools-0.3.0 under Fedora 9. > (Sorry that i make it not faster, but i have no time the last 14 days) > OK, I change the flow.h file after your instruction. > Than ..... > 1. ./configure --> no Problem > 2. make --> the follow message ... > > make > make all-recursive > make[1]: Entering directory `/home/Ralph/bwmd/bwm_tools-0.3.0' > Making all in lib > make[2]: Entering directory `/home/Ralph/bwmd/bwm_tools-0.3.0/lib' > /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c -o libbwm_la-xmlConf.lo `test -f 'xmlConf.c' || echo './'`xmlConf.c > gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.o > In file included from ../include/flow.h:32, > from ../include/autoclass.h:30, > from xmlConf.c:33: > /usr/include/linux/netfilter.h:40: error: expected specifier-qualifier-list before '__u32' > make[2]: *** [libbwm_la-xmlConf.lo] Fehler 1 > make[2]: Leaving directory `/home/Ralph/bwmd/bwm_tools-0.3.0/lib' > make[1]: *** [all-recursive] Fehler 1 > make[1]: Leaving directory `/home/Ralph/bwmd/bwm_tools-0.3.0' > make: *** [all] Fehler 2 > > Hope it will help that you find the problem ;-) > > I will try to check my second problem this week. > Than i send you the backtrace. Sure you applied the patch I sent to the list? -N |
|
From: <lie...@we...> - 2008-09-01 02:14:57
|
Good Morning Nigel,
this evening i test the installation from bwm_tools-0.3.0 under Fedora 9.
(Sorry that i make it not faster, but i have no time the last 14 days)
OK, I change the flow.h file after your instruction.
Than .....
1. ./configure --> no Problem
2. make --> the follow message ...
make
make all-recursive
make[1]: Entering directory `/home/Ralph/bwmd/bwm_tools-0.3.0'
Making all in lib
make[2]: Entering directory `/home/Ralph/bwmd/bwm_tools-0.3.0/lib'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c -o libbwm_la-xmlConf.lo `test -f 'xmlConf.c' || echo './'`xmlConf.c
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.o
In file included from ../include/flow.h:32,
from ../include/autoclass.h:30,
from xmlConf.c:33:
/usr/include/linux/netfilter.h:40: error: expected specifier-qualifier-list before '__u32'
make[2]: *** [libbwm_la-xmlConf.lo] Fehler 1
make[2]: Leaving directory `/home/Ralph/bwmd/bwm_tools-0.3.0/lib'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/Ralph/bwmd/bwm_tools-0.3.0'
make: *** [all] Fehler 2
Hope it will help that you find the problem ;-)
I will try to check my second problem this week.
Than i send you the backtrace.
Best regards
Ralph
> -----Ursprüngliche Nachricht-----
> Von: "Nigel Kukard" <nk...@lb...>
> Gesendet: 12.08.08 11:11:04
> An: Bandwidth Management Tools General & Technical Discussions <bwm...@li...>
> Betreff: Re: [bwm-tools-tech] bwmd crash 3-4 times the day
> Hi,
>
> > at first i hope you find a solution with the fedora 8 and 9, because i
> > have the same problem as
> > Jonathan. (I post it in May)
> >
> > But now i have another problem.
> >
> > In the moment my server works with Suse-Linus 9.2, an older version, but
> > i update the system regularly.
> > Until last Wednesday , i work with bwm_tools 0.2.2.
> > But in the last month i have the problem, that the bwmd process crash
> > 5-6 times daily when i have much
> > traffic over the net.
> > After this, i have no traffic over the net. (think you suspect this)
> >
> > If i start bwmd again, all work fine again.
> >
> > On Wedensday evening i update the bwm_tools to the 0.3.0 version.
> > Now i think it works a little bit better, but i have always 2-4 bwmd
> > crash daily.
> >
> > Where is my problem ?
> >
> > I use
> > - rrdtool 1.2.25,
> > - glibs 2.16.5,
> > - iptables 1.4.1.1,
> > - bind 9.5.0.P2.
>
> Please backtrace a coredump and reply with the results.
>
> Attached a patch which should fix the problem under Fedora wrt building.
> Please let me know if it works.
>
> -N
>
>
>
> <hr>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>
> <hr>
> _______________________________________________
> bwm-tools-tech mailing list
> bwm...@li...
> https://lists.sourceforge.net/lists/listinfo/bwm-tools-tech
>
>
________________________________________________________________________
Schon gehört? Bei WEB.DE gibt' s viele kostenlose Spiele:
http://games.entertainment.web.de/de/entertainment/games/free/index.html
|
|
From: Nigel K. <nk...@lb...> - 2008-08-13 06:41:25
|
lie...@we... wrote: > Hi Nigel, > > thanks for the fast answer. > > I will test the patch for Fedora on weekend, then i let you know. > > Now a silly question ... > > do you mean the "bwmd -f" function with "backtrace a coredump" ? > > or is in the bwm_tools another troubletool ? > > when i start "bwmd -f" and bwmd crashed, > i become the message "Segmantation fault" > > hope this is what you need, > besides i must look as the backtrace work under Suse-Linux. > Compile bwmd with -g in the CFLAGS, enable core dumping in your shell by using ulimit. When it segfaults, it will generate core.* .... open them up with gdb and do a 'bt' to get a backtrace of where in the code it choked. -N |
|
From: <lie...@we...> - 2008-08-13 00:19:54
|
Hi Nigel, thanks for the fast answer. I will test the patch for Fedora on weekend, then i let you know. Now a silly question ... do you mean the "bwmd -f" function with "backtrace a coredump" ? or is in the bwm_tools another troubletool ? when i start "bwmd -f" and bwmd crashed, i become the message "Segmantation fault" hope this is what you need, besides i must look as the backtrace work under Suse-Linux. Regards Ralph > Hi, > > > at first i hope you find a solution with the fedora 8 and 9, because i > > have the same problem as > > Jonathan. (I post it in May) > > > > But now i have another problem. > > > > In the moment my server works with Suse-Linus 9.2, an older version, but > > i update the system regularly. > > Until last Wednesday , i work with bwm_tools 0.2.2. > > But in the last month i have the problem, that the bwmd process crash > > 5-6 times daily when i have much > > traffic over the net. > > After this, i have no traffic over the net. (think you suspect this) > > > > If i start bwmd again, all work fine again. > > > > On Wedensday evening i update the bwm_tools to the 0.3.0 version. > > Now i think it works a little bit better, but i have always 2-4 bwmd > > crash daily. > > > > Where is my problem ? > > > > I use > > - rrdtool 1.2.25, > > - glibs 2.16.5, > > - iptables 1.4.1.1, > > - bind 9.5.0.P2. > > Please backtrace a coredump and reply with the results. > > Attached a patch which should fix the problem under Fedora wrt building. > Please let me know if it works. > > -N > > > > <hr> > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > <hr> > _______________________________________________ > bwm-tools-tech mailing list > bwm...@li... > https://lists.sourceforge.net/lists/listinfo/bwm-tools-tech > > _________________________________________________________________________ In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114 |
|
From: Nigel K. <nk...@lb...> - 2008-08-12 09:10:31
|
Hi, > at first i hope you find a solution with the fedora 8 and 9, because i > have the same problem as > Jonathan. (I post it in May) > > But now i have another problem. > > In the moment my server works with Suse-Linus 9.2, an older version, but > i update the system regularly. > Until last Wednesday , i work with bwm_tools 0.2.2. > But in the last month i have the problem, that the bwmd process crash > 5-6 times daily when i have much > traffic over the net. > After this, i have no traffic over the net. (think you suspect this) > > If i start bwmd again, all work fine again. > > On Wedensday evening i update the bwm_tools to the 0.3.0 version. > Now i think it works a little bit better, but i have always 2-4 bwmd > crash daily. > > Where is my problem ? > > I use > - rrdtool 1.2.25, > - glibs 2.16.5, > - iptables 1.4.1.1, > - bind 9.5.0.P2. Please backtrace a coredump and reply with the results. Attached a patch which should fix the problem under Fedora wrt building. Please let me know if it works. -N |
|
From: <ral...@ra...> - 2008-08-12 09:04:49
|
ralph buchmann Good Morning Nigel, at first i hope you find a solution with the fedora 8 and 9, because i have the same problem as Jonathan. (I post it in May) But now i have another problem. In the moment my server works with Suse-Linus 9.2, an older version, but i update the system regularly. Until last Wednesday , i work with bwm_tools 0.2.2. But in the last month i have the problem, that the bwmd process crash 5-6 times daily when i have much traffic over the net. After this, i have no traffic over the net. (think you suspect this) If i start bwmd again, all work fine again. On Wedensday evening i update the bwm_tools to the 0.3.0 version. Now i think it works a little bit better, but i have always 2-4 bwmd crash daily. Where is my problem ? I use - rrdtool 1.2.25, - glibs 2.16.5, - iptables 1.4.1.1, - bind 9.5.0.P2. Regards Ralph |
|
From: Nigel K. <nk...@lb...> - 2008-08-09 15:32:53
|
Will try install fedora and see if I can fix it for you -N Jonathan Hoover wrote: > Looks pretty similar with 0.3.0... > > [root@bhnet bwm_tools-0.3.0]# make > make all-recursive > make[1]: Entering directory `/root/bwm_tools-0.3.0' > Making all in lib > make[2]: Entering directory `/root/bwm_tools-0.3.0/lib' > /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I.. -I../include -pthread -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 > -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP > -MF .deps/libbwm_la-xmlConf.Tpo -c -o libbwm_la-xmlConf.lo `test -f > 'xmlConf.c' || echo './'`xmlConf.c > mkdir .libs > gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT > libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c > xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.o > In file included from ../include/flow.h:31, > from ../include/autoclass.h:30, > from xmlConf.c:33: > /usr/include/linux/netfilter.h:40: error: expected > specifier-qualifier-list before '__u32' > make[2]: *** [libbwm_la-xmlConf.lo] Error 1 > make[2]: Leaving directory `/root/bwm_tools-0.3.0/lib' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/bwm_tools-0.3.0' > make: *** [all] Error 2 > > > Date: Fri, 8 Aug 2008 18:25:21 +0000 > > From: nk...@lb... > > To: bwm...@li... > > Subject: Re: [bwm-tools-tech] Errors during make > > > > > Hello, running fedora 8. Ran configure --with-rrdtool-source. Seemed > > > fine. On make, got the errors below. Any thoughts on what I might be > > > doing wrong? > > > > > > [root@bhnet bwm_tools-200603080716]# make > > > > Could you try the latest stable release? its dated 2008-01 > > > > -N |
|
From: Jonathan H. <jon...@ho...> - 2008-08-08 18:42:41
|
Looks pretty similar with 0.3.0... [root@bhnet bwm_tools-0.3.0]# makemake all-recursivemake[1]: Entering directory `/root/bwm_tools-0.3.0'Making all in libmake[2]: Entering directory `/root/bwm_tools-0.3.0/lib'/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c -o libbwm_la-xmlConf.lo `test -f 'xmlConf.c' || echo './'`xmlConf.cmkdir .libs gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.oIn file included from ../include/flow.h:31, from ../include/autoclass.h:30, from xmlConf.c:33:/usr/include/linux/netfilter.h:40: error: expected specifier-qualifier-list before '__u32'make[2]: *** [libbwm_la-xmlConf.lo] Error 1make[2]: Leaving directory `/root/bwm_tools-0.3.0/lib'make[1]: *** [all-recursive] Error 1make[1]: Leaving directory `/root/bwm_tools-0.3.0'make: *** [all] Error 2> Date: Fri, 8 Aug 2008 18:25:21 +0000> From: nk...@lb...> To: bwm...@li...> Subject: Re: [bwm-tools-tech] Errors during make> > > Hello, running fedora 8. Ran configure --with-rrdtool-source. Seemed > > fine. On make, got the errors below. Any thoughts on what I might be > > doing wrong?> > > > [root@bhnet bwm_tools-200603080716]# make> > Could you try the latest stable release? its dated 2008-01> > -N> |
|
From: Nigel K. <nk...@lb...> - 2008-08-08 18:25:23
|
> Hello, running fedora 8. Ran configure --with-rrdtool-source. Seemed > fine. On make, got the errors below. Any thoughts on what I might be > doing wrong? > > [root@bhnet bwm_tools-200603080716]# make Could you try the latest stable release? its dated 2008-01 -N |
|
From: Jonathan H. <jon...@ho...> - 2008-08-08 16:52:21
|
Hello, running fedora 8. Ran configure --with-rrdtool-source. Seemed fine. On make, got the errors below. Any thoughts on what I might be doing wrong? [root@bhnet bwm_tools-200603080716]# makemake all-recursivemake[1]: Entering directory `/root/bwm_tools-200603080716'Making all in libmake[2]: Entering directory `/root/bwm_tools-200603080716/lib'make[3]: Entering directory `/root/bwm_tools-200603080716'make[3]: Leaving directory `/root/bwm_tools-200603080716'if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF ".deps/libbwm_la-xmlConf.Tpo" -c -o libbwm_la-xmlConf.lo `test -f 'xmlConf.c' || echo './'`xmlConf.c; \ then mv -f ".deps/libbwm_la-xmlConf.Tpo" ".deps/libbwm_la-xmlConf.Plo"; else rm -f ".deps/libbwm_la-xmlConf.Tpo"; exit 1; fi gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.oIn file included from ../include/flow.h:31, from ../include/autoclass.h:30, from xmlConf.c:33:/usr/include/linux/netfilter.h:40: error: expected specifier-qualifier-list before '__u32'make[2]: *** [libbwm_la-xmlConf.lo] Error 1make[2]: Leaving directory `/root/bwm_tools-200603080716/lib'make[1]: *** [all-recursive] Error 1make[1]: Leaving directory `/root/bwm_tools-200603080716'make: *** [all] Error 2 |
|
From: Nigel K. <nk...@lb...> - 2008-05-20 18:33:34
|
> /usr/include/linux/netfilter.h:40: error: expected > specifier-qualifier-list before '__u32' Looks like a problem with your netfilter.h file. There is probably an include missing. Maybe ask on your distributions forums, if the say its a bug in bwmtools I'll hack around it. -N |
|
From: <ral...@ra...> - 2008-05-20 07:59:34
|
Hello from Germany,
i have a little problem and hope you can help me.
I try to install a new server.
My linux is the new Fedora 9 with Kernel 2.6.25.3, iproute 2.6.26-1 and iptables-1.4.0.4.
So i download bwmd-0.3.0 and start ./configure without a problem.
But then i go to the next step make, i become the follow result .......
ralph buchmann
email: ral...@t-...
make all-recursive
make[1]: Entering directory `/home/Ralph/bwmd/bwm_tools-0.3.0'
Making all in lib
make[2]: Entering directory `/home/Ralph/bwmd/bwm_tools-0.3.0/lib'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c -o libbwm_la-xmlConf.lo `test -f 'xmlConf.c' || echo './'`xmlConf.c
gcc -DHAVE_CONFIG_H -I. -I.. -I../include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libxml2 -DLOG_DIR=\"/var/bwm_tools\" -g -O2 -MT libbwm_la-xmlConf.lo -MD -MP -MF .deps/libbwm_la-xmlConf.Tpo -c xmlConf.c -fPIC -DPIC -o .libs/libbwm_la-xmlConf.o
In file included from ../include/flow.h:31,
from ../include/autoclass.h:30,
from xmlConf.c:33:
/usr/include/linux/netfilter.h:40: error: expected specifier-qualifier-list before '__u32'
make[2]: *** [libbwm_la-xmlConf.lo] Fehler 1
make[2]: Leaving directory `/home/Ralph/bwmd/bwm_tools-0.3.0/lib'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/Ralph/bwmd/bwm_tools-0.3.0'
make: *** [all] Fehler 2
Now, what can i do ??
Best Regards
Ralph
|
|
From: Nigel K. <nk...@lb...> - 2008-05-05 18:25:51
|
Hi, > I work with an ISP in Nigeria and i happen to be the > Network Administrator of that company. I need your help as regard the > configuration of bwm-tool from the scratch. I started sometimes but i > got stucked on the way because i could not understand some of the > things it asked me to install. Moreso, does the bwm-tools has > graphical interface (GUI)? > I will appreciate if i could be helped to make it work. There are currently three documents which describe configuring bwm tools... http://www.murder4al.be/ http://www.bwmtools.org/manual.pdf http://www.bwmtools.org/BMO-Notes-Final3.pdf I suggest you read them over and try some of the examples, as BWM Tools is based mostly on iptables rules ... reading iptables howto's should also give you some insight. Regards Nigel |
|
From: tope o. <gen...@ya...> - 2008-05-05 16:32:34
|
Hello Sir,
I work with an ISP in Nigeria and i happen to be the Network Administrator of that company. I need your help as regard the configuration of bwm-tool from the scratch. I started sometimes but i got stucked on the way because i could not understand some of the things it asked me to install. Moreso, does the bwm-tools has graphical interface (GUI)?
I will appreciate if i could be helped to make it work.
Thanks.
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. |
|
From: Ibrahim S. O. <iom...@gm...> - 2008-05-05 00:41:23
|
Greetings, Please i need help. Attached are my flow file, my graph script and my iptables-restore file. I see packets in my bwmd chain and bwm_monitor seems to be working fine but my graphs are empty. Every few days or so I can see small activity on some graphs but basically they are empty. Can someone tell me what I am doing wrong? iomari |
|
From: Nigel K. <nk...@lb...> - 2008-04-10 08:05:31
|
> The version I used is stable 0.3.0 from January 2, 2008. It looks > like the last snapshot was March 8, 2006 (shown on sourceforge). Is > the March 8, 2006 snapshot a later revision than the stable release > on January 2, 2008? Ah you right, latest is the stable. You're using the right version. > > > > > > There is an initial burst of data let through, then the stream > > > sputters and dies. It looks to me like it creates a loop for the > > > data which causes trouble. It's only processing one 256Kbit/sec flow > > > via a fast ethernet interface on a Celeron 2.53GHz (Pentium D > > > generation) with 512MB RAM. The machine is only running bwm_tools > > > and is dedicated to this testing process. Our production machine > > > will be much beefier and will have multiple gigabit interfaces run > > > in bridge mode (packets hitting the FORWARD chains mainly). > > > > > > So, my question is, where does bwmd reinsert the packets that it > > > processes? > > > > Kernel sends the packet header to bwmd, it then acks or nacks it back > > to the kernel. I think there is one or two threads which handle this, > > I'll have to check and make sure if you get stuck. > > > > So only the header is sent to bwmd. bwmd then tells the kernel queue > to trash the packet or let it through. It doesn't actually insert > itself into the processing of the stream and just issues instructions > to the kernel about what to do with packets currently in transit. Am > I understanding correctly? Well, there is a queue of packets that need a verdict to be sent for. BWMD sends verdicts in the order it see's fit to shape the traffic. It may not be in a FIFO order. So you could say the kernel keeps the packets in a buffer and only sends through through when BWMD has seen them and decided what to do with them. > So, bwmd acks or nacks the packets at the end of filter INPUT/OUTPUT, > but the packet never leaves the kernel queue. It just gets > temporarily held for the results of additional userspace processing. > If that's the case, then there really isn't any opportunity to cause > a data loop. It must be something else, if that's the case. Correct. I was pondering about using tun/tap to bring the queueing to userspace entirely. Problem is, you create a device which is handled by userspace ... but then what? you'll then need some magic to make sure all traffic hits it, then more magic to get the traffic out again ... so yea. > > > I looked through the code and it was obvious to me that it just > > > waits for packets, checks link budgets, trims flows, but then I lose > > > track of where that data exits bwmd and heads back into the > > > networking stack of the OS. I'm sure I just missed it while skimming > > > the code. > > > > The packet header is added to a queue after its been received. There > > is code there regarding the kernel queue which acks the packet ... if > > you have trouble finding it, let me know and I'll check the code and > > show you :) > > I suspected that the code I needed to look at was actually kernel (or > kernel module) code. What you're saying would seem to confirm that. > Am I understanding correctly? BWMD uses netlink sockets to communicate the packets verdict back to the kernel. If its a BWMD problem, you'll need to look in the BWMD source. There is one such file that handles the queue interface, then I think the main BWMD daemon handles the inbound packet headers and sending the verdicts back. Its like only 3 lines of code, so its easily missed. > > > Can anyone lend some insight on this? To me, it is most important > > > that it work well with the FORWARD chains, which seems to be the > > > original design intent, but it would be nice if it could be used for > > > limiting flows originating/terminating on the host itself, as well. > > > > Both ways should work, I've tested both :) I'm curious as to those > > errors you're getting. > > It could just be that the netfilter code was changed up at some point > after you last tested. I know from experience that the linux kernels > are in a constant state of flux. Its possible, but I think that would more constitute a bug if its the Kernel that changed? > > > > > Thanks in advance. If I've boneheaded something, please be gentle. > > > If this suits our basic needs, we may very well fund future > > > development to smooth some rough edges and extend the features > > > (particularly, support for more threads). Heck, I might even write a > > > little code and/or documentation. > > > > That would be excellent and very much appreciated. > > > > We were also looking at tun/tap support so it would run on other > > OS's ... but unfortunately funding is a bit of an issue :( > > The only OS's we're interested in are linux and BSD variants. *Maybe* > a Solaris version might be useful, but only with much more threading > (think T1 or T2 processors). *nod* > I don't know your time and financial constraints. How much do you > think you'd need to extend the threading model to scale to 8 or more > processor cores? Right now, it appears there are 4 threads with the > bulk of the processor intensive work done on 2 of those threads. We'd > like to deploy this on a dual socket quad core (8 cores total) > system. In a perfect world, we'd like to be able to handle a few > thousand rules, eight gigabit interfaces, and about 400Mbits/sec of > throughput. Thats pretty hard to say, let me think about it a bit. Possibly contact me offlist on nk...@lb... to discuss. -N |
|
From: Andrew K. <and...@ad...> - 2008-04-09 20:08:50
|
Reply is inline below. On 9 Apr 2008 at 15:04, Nigel Kukard wrote: > > > However, we cannot do the same with the OUTPUT chain of the filter > > table. If we jump those packets over to bwmd, bwmd starts spewing > > messages related to truncation. > > Please provide full logs. Have you tried latest snapshot? I'll look around to see what logs there are. The problem is easily reproducible, so it should be easy to create additional logging if needed. The version I used is stable 0.3.0 from January 2, 2008. It looks like the last snapshot was March 8, 2006 (shown on sourceforge). Is the March 8, 2006 snapshot a later revision than the stable release on January 2, 2008? > > > There is an initial burst of data let through, then the stream > > sputters and dies. It looks to me like it creates a loop for the > > data which causes trouble. It's only processing one 256Kbit/sec flow > > via a fast ethernet interface on a Celeron 2.53GHz (Pentium D > > generation) with 512MB RAM. The machine is only running bwm_tools > > and is dedicated to this testing process. Our production machine > > will be much beefier and will have multiple gigabit interfaces run > > in bridge mode (packets hitting the FORWARD chains mainly). > > > > So, my question is, where does bwmd reinsert the packets that it > > processes? > > Kernel sends the packet header to bwmd, it then acks or nacks it back > to the kernel. I think there is one or two threads which handle this, > I'll have to check and make sure if you get stuck. > So only the header is sent to bwmd. bwmd then tells the kernel queue to trash the packet or let it through. It doesn't actually insert itself into the processing of the stream and just issues instructions to the kernel about what to do with packets currently in transit. Am I understanding correctly? > > wire in > > eth0 > > raw PREROUTING > > conntrack > > mangle PREROUTING > > routing > > mangle INPUT (here we mark inbound packets for bwmd) > > filter INPUT (at the end of this chain, we jump to bwmd) > > application (browser, ftp client, web server, whatever) > > --- > > application > > routing > > raw OUTPUT > > conntrack > > mangle OUTPUT (here we mark outbound packets for bwmd) > > routing (second pass in case mangle changed something) > > filter OUTPUT (logically, this is what should jump to bwmd, but > > doesn't work) mangle POSTROUTING eth0 wire out > > Thats the flow ..... bwmtools needs to ack or nack the packets in the > kernel queue. This would occur when you jump to bwmd. Packets which > are ack'd will come out of the kernel queue and carry on transversal > of the chains. So, bwmd acks or nacks the packets at the end of filter INPUT/OUTPUT, but the packet never leaves the kernel queue. It just gets temporarily held for the results of additional userspace processing. If that's the case, then there really isn't any opportunity to cause a data loop. It must be something else, if that's the case. > > > > I looked through the code and it was obvious to me that it just > > waits for packets, checks link budgets, trims flows, but then I lose > > track of where that data exits bwmd and heads back into the > > networking stack of the OS. I'm sure I just missed it while skimming > > the code. > > The packet header is added to a queue after its been received. There > is code there regarding the kernel queue which acks the packet ... if > you have trouble finding it, let me know and I'll check the code and > show you :) I suspected that the code I needed to look at was actually kernel (or kernel module) code. What you're saying would seem to confirm that. Am I understanding correctly? > > > > Can anyone lend some insight on this? To me, it is most important > > that it work well with the FORWARD chains, which seems to be the > > original design intent, but it would be nice if it could be used for > > limiting flows originating/terminating on the host itself, as well. > > Both ways should work, I've tested both :) I'm curious as to those > errors you're getting. It could just be that the netfilter code was changed up at some point after you last tested. I know from experience that the linux kernels are in a constant state of flux. I'll see what I can do to better pinpoint what is happening and the cause. > > > > Thanks in advance. If I've boneheaded something, please be gentle. > > If this suits our basic needs, we may very well fund future > > development to smooth some rough edges and extend the features > > (particularly, support for more threads). Heck, I might even write a > > little code and/or documentation. > > That would be excellent and very much appreciated. > > We were also looking at tun/tap support so it would run on other > OS's ... but unfortunately funding is a bit of an issue :( The only OS's we're interested in are linux and BSD variants. *Maybe* a Solaris version might be useful, but only with much more threading (think T1 or T2 processors). I don't know your time and financial constraints. How much do you think you'd need to extend the threading model to scale to 8 or more processor cores? Right now, it appears there are 4 threads with the bulk of the processor intensive work done on 2 of those threads. We'd like to deploy this on a dual socket quad core (8 cores total) system. In a perfect world, we'd like to be able to handle a few thousand rules, eight gigabit interfaces, and about 400Mbits/sec of throughput. Sincerely, Andrew Kinney President and Chief Technology Officer Advantagecom Networks, Inc. http://www.advantagecom.net phone: 509-522-3696 ext. 101 |
|
From: Nigel K. <nk...@lb...> - 2008-04-09 15:05:19
|
> However, we cannot do the same with the OUTPUT chain of the filter table. If we > jump those packets over to bwmd, bwmd starts spewing messages related to > truncation. Please provide full logs. Have you tried latest snapshot? > There is an initial burst of data let through, then the stream > sputters and dies. It looks to me like it creates a loop for the data which > causes trouble. It's only processing one 256Kbit/sec flow via a fast ethernet > interface on a Celeron 2.53GHz (Pentium D generation) with 512MB RAM. The > machine is only running bwm_tools and is dedicated to this testing process. Our > production machine will be much beefier and will have multiple gigabit > interfaces run in bridge mode (packets hitting the FORWARD chains mainly). > > So, my question is, where does bwmd reinsert the packets that it processes? Kernel sends the packet header to bwmd, it then acks or nacks it back to the kernel. I think there is one or two threads which handle this, I'll have to check and make sure if you get stuck. > wire in > eth0 > raw PREROUTING > conntrack > mangle PREROUTING > routing > mangle INPUT (here we mark inbound packets for bwmd) > filter INPUT (at the end of this chain, we jump to bwmd) > application (browser, ftp client, web server, whatever) > --- > application > routing > raw OUTPUT > conntrack > mangle OUTPUT (here we mark outbound packets for bwmd) > routing (second pass in case mangle changed something) > filter OUTPUT (logically, this is what should jump to bwmd, but doesn't work) > mangle POSTROUTING > eth0 > wire out Thats the flow ..... bwmtools needs to ack or nack the packets in the kernel queue. This would occur when you jump to bwmd. Packets which are ack'd will come out of the kernel queue and carry on transversal of the chains. > I looked through the code and it was obvious to me that it just waits for > packets, checks link budgets, trims flows, but then I lose track of where that > data exits bwmd and heads back into the networking stack of the OS. I'm sure I > just missed it while skimming the code. The packet header is added to a queue after its been received. There is code there regarding the kernel queue which acks the packet ... if you have trouble finding it, let me know and I'll check the code and show you :) > Can anyone lend some insight on this? To me, it is most important that it work > well with the FORWARD chains, which seems to be the original design intent, but > it would be nice if it could be used for limiting flows originating/terminating > on the host itself, as well. Both ways should work, I've tested both :) I'm curious as to those errors you're getting. > Thanks in advance. If I've boneheaded something, please be gentle. If this > suits our basic needs, we may very well fund future development to smooth some > rough edges and extend the features (particularly, support for more threads). > Heck, I might even write a little code and/or documentation. That would be excellent and very much appreciated. We were also looking at tun/tap support so it would run on other OS's ... but unfortunately funding is a bit of an issue :( Kind regards Nigel |
|
From: Andrew K. <and...@ad...> - 2008-04-09 09:39:29
|
Hello, I have bwm_tools-0.3.0 running on CentOS 5 with kernel 2.6.18-53.1.14.el5 SMP i686/i386 (32-bit). There were some minor bumps, but I got it working in an evening. This is a test installation on a host with a single interface. On the filter table, we can jump packets from the end of the INPUT chain to the bwmd chain where they get queued out to bwmd in userspace. All packets incoming to the host are properly rate limited. However, we cannot do the same with the OUTPUT chain of the filter table. If we jump those packets over to bwmd, bwmd starts spewing messages related to truncation. There is an initial burst of data let through, then the stream sputters and dies. It looks to me like it creates a loop for the data which causes trouble. It's only processing one 256Kbit/sec flow via a fast ethernet interface on a Celeron 2.53GHz (Pentium D generation) with 512MB RAM. The machine is only running bwm_tools and is dedicated to this testing process. Our production machine will be much beefier and will have multiple gigabit interfaces run in bridge mode (packets hitting the FORWARD chains mainly). So, my question is, where does bwmd reinsert the packets that it processes? As I understand it, here is the path a packet and its reply takes without bwmd. We're starting with the packet coming in the interface, going to the application, and then back out the interface (flowing top to bottom, input towards output). I've excluded NAT because we're not using it right now. wire in eth0 raw PREROUTING conntrack mangle PREROUTING routing mangle INPUT (here we mark inbound packets for bwmd) filter INPUT (at the end of this chain, we jump to bwmd) application (browser, ftp client, web server, whatever) --- application routing raw OUTPUT conntrack mangle OUTPUT (here we mark outbound packets for bwmd) routing (second pass in case mangle changed something) filter OUTPUT (logically, this is what should jump to bwmd, but doesn't work) mangle POSTROUTING eth0 wire out I looked through the code and it was obvious to me that it just waits for packets, checks link budgets, trims flows, but then I lose track of where that data exits bwmd and heads back into the networking stack of the OS. I'm sure I just missed it while skimming the code. Can anyone lend some insight on this? To me, it is most important that it work well with the FORWARD chains, which seems to be the original design intent, but it would be nice if it could be used for limiting flows originating/terminating on the host itself, as well. Thanks in advance. If I've boneheaded something, please be gentle. If this suits our basic needs, we may very well fund future development to smooth some rough edges and extend the features (particularly, support for more threads). Heck, I might even write a little code and/or documentation. Sincerely, Andrew Kinney CTO, Advantagecom Networks http://www.simplywebhosting.com |
11 messages has been excluded from this view by a project administrator.
