Re: [AOLSERVER] BIG problem with Tcl8.4.(1|2)
On Thursday 27 March 2003 22:28, you wrote: Yes, of course, and it can often breaks things, right? Most users of cd/pwd seem to want to neglect the fact that the pwd state is per-process not per-thread, so perhaps it would be simpler just to give them that, thus side-stepping the locking issues. Eh, the cwd is the thing which is used by most path-related sys/lib calls to resolve the absolute path of the file. It is tracked in the kernel, not in the process, so in order to make this happen, you ought to intercept *all* of the sys/lib calls fiddling with paths. Now, Tcl with its virtual filesystem *might* achieve this, since it really isolates the upper layers from the OS-specifics. But, if you ask me, I think this is voodoo. Therefore, assume a TLS cd/pwd implementation, where each and every thread has it's OWN independent current working directory. Does any code break because of this? In other words, is there any code anywhere that both, a), properly treats pwd as per-process not per-thread, and b), DEPENDS on the sharing of pwd across threads for its correct behavior? In an ideal world, this is correct. It holds true until somebody gives you some extension which calls os-calls directly, not using your own notion of cwd. This is the time when things start to be very interesting (and cost lot of time/money to locate them). I know this per-thread working directory thing is very appealing but it should have been designed so by the standard and/or kernel-makers. If we try to emulate this on the very high level, we'll end up in a mess, sooner or later. What's the TSD? It is the term used throughout the Tcl sources to refer to thread specific data. In AOLserver, people talk about thread local storage which is essentially the same thing. I wasn't trying to protect myself, I was hypothesizing about possible designs/implementations for fixing the problem in Tcl. :) To be honest, I was also playing with this idea, but after giving it a serious thought, I've abandoned it. The fact that some system calls apparently change pwd and then change it back when they complete is really obnoxious, because that means that for proper mt-safe operation, those system calls MUST expose a mutex which any of YOUR pwd-changing code will explicitly lock and unlock as well. This is a general obnoxious feature of multi-threaded programming with multiple libraries - a given mutex sometimes must be seen and used across ALL libraries, not just within one library. Yes, some library calls, like realpath() in MacOSX (see my other posting) are doing this. They call chdir/fchdir syscalls without you knowing this possibly interacting with your own code in a different thread. This has driven me nuts for couple of days while porting our app to Darwin. Yet, there is no word about that in the manpage! I think this is one area where standard-makers must do some more work. The fact as it is now, I'm grepping thru all code, looking for obvious calls that might change cwd (chdir/fchdir). This covers most of the cases. But, there are hidden ones, and you just can't fight them back until they show they ugly head. I think I will discuss this issue with some Tcl people and try to produce a list of Tcl functions which might directly or indirectly change your working directory. Funny think about the MacOSX: even the innocent [pwd] changed the current dir! This is really crazy! Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
On Thu, 27 Mar 2003, Ayan George wrote:
I'm trying to register a procedure to handle:
http://www.foo.net/~user/
type URLs. I want to redirect the request to:
http://members.foo.net/user/
I tried a couple of registerd procedures like:
ns_register_proc-noinherit GET {/~*} tilde_redirect
ns_register_proc-noinherit POST{/~*} tilde_redirect
But the expression doesn't seem to match
anything. I'm sure there is something very
simple I'm overlooking.
Does anyone have any suggestions?
I suspect that using -noinherit options don't mix very well with
wildcard *. I belive that there is no simple solution other that
ns_register_procGET {/~*} tilde_redirect
but it does more than you probably want.
Maybe you should look at ns_register_dir module from Zjednoczenie.com
AOLserver 3.x distro from http://miniacs.zjednoczenie.com/download/nsdz6.tgz
It is based on example from older AOLserver docs which can be found here:
http://www.tcl.tk/man/aolserver3.0/c-app2.htm.
It supports general url - directory mapping but also mappings /~user to
user home directory.
Module ns_register_dir, after enhancements, was finally renamed to
ns_url2file which I've described in my proposal sent to the list a few
weeks ago. It could be reached at:
http://miniacs.zjednoczenie.com/download/vserv2.tgz
--tkosiak
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
[AOLSERVER] problems with aolserver4 + openacs
Hi, Today i tried to run the new aolserver beta (did not try any other aolserver-4-beta till now), with openacs. It seems as if there are problems with the templating system on the aolserver side. In my master template there are some if,include and multiple tags. When trying to access the webstats area or some static html pages everything works ok (pages are devlivered), but when I try to get a page that is using the openacs templating system there is no answer. I could trace the problem to the function ns_adp_parse. That function does not return and does not deliver an error either. It seems to break when compiling tags defined by openacs. In the ps axf output I can see that the request thread (process) becomes a zombie. After that no other request are answered anymore (other static html pages are not working as well). When I kill the server a core dump is created. has anyone else tried aolserver4b4 and openacs and had similar problems? I did not have any problems compiling aolserver and the modules needed for openacs. The system is Redhat 8.0 with kernel 2.4.19. TIA, peter -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] Aolserver 3.42 and nsunix
Hi! Has anyone got nsvhr/nsunix to work with Aolserver 3.42? With 3.2 I have no problems, but the same configurations don't work with 3.42. As soon as I connect to the servers via nsvhr/nsunix they segfault. Connecting to the ports directly works without any problems. Thanks wiwo -- Digital Concepts Ideen-Konzepte-Lösungen [EMAIL PROTECTED] www.digital-concepts.com Mobil: +43 699 / 20 88 13 51 Büro: +43 732 / 77 27 27 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Aolserver 3.42 and nsunix
Wolfgang, I had the exact same problem quite a while ago. I couldn't pinpoint the problem so I wrote my own (smaller and simpler) front end that does the same thing. You can find it at: http://www.ayan.net/software/nsvirthost/nsvirthost-0.0.1.tar.gz It works pretty well. If you have any questions about compiling or configuring it, let me know. -ayan On Fri, 28 Mar 2003, Wolfgang Winkler wrote: Hi! Has anyone got nsvhr/nsunix to work with Aolserver 3.42? With 3.2 I have no problems, but the same configurations don't work with 3.42. As soon as I connect to the servers via nsvhr/nsunix they segfault. Connecting to the ports directly works without any problems. Thanks wiwo -- Digital Concepts Ideen-Konzepte-Lösungen [EMAIL PROTECTED] www.digital-concepts.com Mobil: +43 699 / 20 88 13 51 Büro: +43 732 / 77 27 27 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
Tomasz, It seems ns_register_proc ignores glob characters at the end of the pattern. ns_register_filter works fine. Thanks for the help. -ayan On Fri, 28 Mar 2003, Tomasz Kosiak wrote: It supports general url - directory mapping but also mappings /~user to user home directory. Module ns_register_dir, after enhancements, was finally renamed to ns_url2file which I've described in my proposal sent to the list a few weeks ago. It could be reached at: http://miniacs.zjednoczenie.com/download/vserv2.tgz --tkosiak -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
On Fri, 28 Mar 2003, Ayan George wrote: Tomasz, It seems ns_register_proc ignores glob characters at the end of the pattern. ns_register_filter works fine. Indeed they are implemented very differently: - ns_register_filter uses somthing like string match on url pattern - ns_register_proc uses urltrie structure which allows to find longest matching url pattern with some support for wildcards --tkosiak On Fri, 28 Mar 2003, Tomasz Kosiak wrote: It supports general url - directory mapping but also mappings /~user to user home directory. Module ns_register_dir, after enhancements, was finally renamed to ns_url2file which I've described in my proposal sent to the list a few weeks ago. It could be reached at: http://miniacs.zjednoczenie.com/download/vserv2.tgz --tkosiak -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Aolserver 3.42 and nsunix
Hi! Thanks for your response. Some help to compile would be very nice. If I just type make I get some warnings and this error: main.c: In function `Np_UdsProxy': main.c:406: structure has no member named `msg_accrights' main.c:407: structure has no member named `msg_accrightslen' main.c: At top level: main.c:493: `domain_match' used prior to declaration main.c:514: `sigpipeh' used prior to declaration I'm sure I have to do something with the Makefile :-) wiwo On Friday 28 March 2003 14:07, you wrote: Wolfgang, I had the exact same problem quite a while ago. I couldn't pinpoint the problem so I wrote my own (smaller and simpler) front end that does the same thing. You can find it at: http://www.ayan.net/software/nsvirthost/nsvirthost-0.0.1.tar.gz It works pretty well. If you have any questions about compiling or configuring it, let me know. -ayan On Fri, 28 Mar 2003, Wolfgang Winkler wrote: Hi! Has anyone got nsvhr/nsunix to work with Aolserver 3.42? With 3.2 I have no problems, but the same configurations don't work with 3.42. As soon as I connect to the servers via nsvhr/nsunix they segfault. Connecting to the ports directly works without any problems. Thanks wiwo -- Digital Concepts Ideen-Konzepte-Lösungen [EMAIL PROTECTED] www.digital-concepts.com Mobil: +43 699 / 20 88 13 51 Büro: +43 732 / 77 27 27 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- Digital Concepts Ideen-Konzepte-Lösungen [EMAIL PROTECTED] www.digital-concepts.com Mobil: +43 699 / 20 88 13 51 Büro: +43 732 / 77 27 27 -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Aolserver 3.42 and nsunix
Has anyone got nsvhr/nsunix to work with Aolserver 3.42? With 3 .2 I have no problems, but the same configurations don't work with 3.42. nsvhr/nsunix are probably broken for 3.4.2 but they work for 3.5.1 without problems. Be sure to copy it from CVS. Daniel P. Stasinski Software Engineer Mayor Pharmaceutical Laboratories [EMAIL PROTECTED] -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Fwd: AOLServer 4
We're trying to get in touch with the PHP team to address. This is one of the potential side effects of moving to 4.0 from prior 3.x versions since virtual server support is now back. Pretty easy to address - be sure to check out Mark's porting document: http://aolserver.sourceforge.net/docs/devel/c/ as4_moduleportingguide.html. Stay tuned! - Nathan On Friday, March 28, 2003, at 10:17 AM, Andrey Chichak wrote: It works! But only when for 1 virtual host enabled. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
Certainly something we can look into to - ideally in a way that would keep backwards compatibility. Want to take a crack at a proposal that address this issue across all effected procs? - Nathan On Friday, March 28, 2003, at 10:20 AM, Ayan George wrote: Why can't we just use POSIX regular expressions for all of the ns_register* procedures? -ayan -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
That sounds like a good idea. Espcially if you make the default behaviour whatever the current behaviour is. This will ensure backwards compatibility (with no changes to existing code). If you want the extra flexibility the regexp option gives you then you add it to your code and chaneg the expressions accordingly. -Original Message- From: AOLserver Discussion [mailto:[EMAIL PROTECTED] Behalf Of Brett Schwarz Sent: Friday, March 28, 2003 3:58 PM To: [EMAIL PROTECTED] Subject: Re: [AOLSERVER] ns_register_proc I agree, but maybe we can add a option to the command, similar to what Tcl's switch and lsearch commands do (i.e. -glob -regexp, etc) --brett On Fri, 2003-03-28 at 07:43, Peter M. Jansson wrote: Why can't we just use POSIX regular expressions for all of the ns_register* procedures? I'd be concerned about REs degrading performance. REs are usually significantly slower than glob matches, and the registered proc matcher will be called a _lot_. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- Brett Schwarz [EMAIL PROTECTED] Very Little -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
Agree. If you want to take a stab at implementing, and can provide a patch, we'll take a look and get it added to the core. Thanks in advance. - Nathan On Friday, March 28, 2003, at 01:17 PM, Tim Moss wrote: That sounds like a good idea. Espcially if you make the default behaviour whatever the current behaviour is. This will ensure backwards compatibility (with no changes to existing code). If you want the extra flexibility the regexp option gives you then you add it to your code and chaneg the expressions accordingly. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
Guys, During my lunch break, I wrote a small program to compare the execution of Tcl_StringMatch() (what ns_register_filter uses to match URLs) and Tcl_RegExpExec() (what I propose ns_register_filter should have the option of using). It looks like the regular expression stuff is just as fast (or slow depending on how you look at it) as the Tcl_StringMatch() we currently use. Of course, I haven't tested it very thouroughly. If you are interested in the code I used, it is here: http://www.ayan.net/software/TclReCmp/ I'd like to take a stab at implementing the RE matching for the ns_register_* procedures if that is okay. -ayan On Fri, 28 Mar 2003, Nathan Folkman wrote: Agree. If you want to take a stab at implementing, and can provide a patch, we'll take a look and get it added to the core. Thanks in advance. - Nathan On Friday, March 28, 2003, at 01:17 PM, Tim Moss wrote: That sounds like a good idea. Espcially if you make the default behaviour whatever the current behaviour is. This will ensure backwards compatibility (with no changes to existing code). If you want the extra flexibility the regexp option gives you then you add it to your code and chaneg the expressions accordingly. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
Thanks! Go for it. :-) Make sure you grab the head version of the code - that will ensure you have the latest 4.0 code. Once you've got something you're happy with, please submit the changes as a patch and we'll review. - Nathan On Friday, March 28, 2003, at 01:29 PM, Ayan George wrote: http://www.ayan.net/software/TclReCmp/ I'd like to take a stab at implementing the RE matching for the ns_register_* procedures if that is okay. -ayan -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Aolserver 3.42 and nsunix
On 2003.03.28, Wolfgang Winkler [EMAIL PROTECTED] wrote: Has anyone got nsvhr/nsunix to work with Aolserver 3.42? With 3.2 I have no problems, but the same configurations don't work with 3.42. As soon as I connect to the servers via nsvhr/nsunix they segfault. Connecting to the ports directly works without any problems. What version of nsvhr and nsunix are you using? Please try the latest ones in CVS -- if they don't build with 3.4.2, let me know and I'll look at a backport. Otherwise, why haven't you upgraded to AOLserver 3.5.x? :-) -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] Bug in tclhttp.c
Hello,
Tcl command ns_http queue $method $url causes access violation in
Aolserver 4.0 beta 4 - note missing headers parameter in the command.
The access violation is due to variable hdrs left uninitialized in the
following block of code
line 126:
case HQueueIdx:
if (objc 4 || objc 6) {
Tcl_WrongNumArgs(interp, 2, objv, method url ?body?
?headers?);
return TCL_ERROR;
}
method = Tcl_GetString(objv[2]);
url= Tcl_GetString(objv[3]);
if (objc 4) {
body = Tcl_GetString(objv[4]);
if (objc 5) {
if (Ns_TclGetSet2(interp, Tcl_GetString(objv[5]), hdrs)
!= TCL_OK) {
return TCL_ERROR;
}
}
else {
hdrs = NULL;
}
}
else {
body = NULL;
}
Last else block needs hdrs=NULL; statement.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Bug in tclhttp.c
Has anyone on the aolserver core team taken a look at libcurl?
http://curl.haxx.se
They claim to be thread safe...
There is a TCL wrapper at
http://personal1.iddeo.es/andresgarci/tclcurl/english/
Doubtless this is old news to many, but it seems like it has so much to
offer :)
jab The TCL native and Aolserver HTTP implementations just seem
to be far behind what this has and all my PHP buddies get to use it as a
builtin :-) /jab
Alfred
On Fri, 28 Mar 2003, Alexander Leyke wrote:
Hello,
Tcl command ns_http queue $method $url causes access violation in
Aolserver 4.0 beta 4 - note missing headers parameter in the command.
The access violation is due to variable hdrs left uninitialized in the
following block of code
line 126:
case HQueueIdx:
if (objc 4 || objc 6) {
Tcl_WrongNumArgs(interp, 2, objv, method url ?body?
?headers?);
return TCL_ERROR;
}
method = Tcl_GetString(objv[2]);
url= Tcl_GetString(objv[3]);
if (objc 4) {
body = Tcl_GetString(objv[4]);
if (objc 5) {
if (Ns_TclGetSet2(interp, Tcl_GetString(objv[5]), hdrs)
!= TCL_OK) {
return TCL_ERROR;
}
}
else {
hdrs = NULL;
}
}
else {
body = NULL;
}
Last else block needs hdrs=NULL; statement.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Bug in tclhttp.c
Hey Alfred, How about using the Tcl wrapper and writing an AOLserver module to add curl support? I'm sure the core team would love a patch. You could verify the thread-safety claims. I'm sure the community would appreciate your work. Pete. Has anyone on the aolserver core team taken a look at libcurl? http://curl.haxx.se They claim to be thread safe... There is a TCL wrapper at http://personal1.iddeo.es/andresgarci/tclcurl/english/ Doubtless this is old news to many, but it seems like it has so much to offer :) jab The TCL native and Aolserver HTTP implementations just seem to be far behind what this has and all my PHP buddies get to use it as a builtin :-) /jab -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Bug in tclhttp.c
I'm close .. I'll need it for a project right after the one I'm finishing up :) Any pointer to a good doc to show me what layer of interface you're talking about or a module that is similar/at the same layer? I take it the TCLcurl is a hand-rolled SWIG-ish kind of interface to the underlying C libs. The API looks like it covers basically all the underlying calls. Alfred -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Ns_PgExec looking in wrong place for plpgsql.so
Lamar Owen wrote: RH8.0 is not binary compatible with previous Red Hat distributions. You might want to recompile AOLserver -- 3.4 will compile fine on RH8. The main issue I had was I am using nsssl.so module, which I didn't have the source for. I thought it might not work on an upgrade from 3.4.2 to 3.5.6. But I gave it a try and upgraded. nsssl.so seemed to load, still need to check it. But once I upgraded, it still segfaulted. Then I remembered the stacksize issue on RH8. My old config file didn't even have a line for that, so I added it, and the segfault went away. The segfaults seem to show up on network related procs. ns_geturl, ns_sockopen so far caused the problem. So I guess two things to remember is: 1. You can't change the library directory for postgres once you install the plpgsql language, without also changing pg_proc.procsrc value accordingly. 2. Stacksize needs to be set to something above the default on RH8, even for AOLserver 3.4.2. --Tom Jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Bug in tclhttp.c
Alfred Werner wrote: They claim to be thread safe... There is a TCL wrapper at http://personal1.iddeo.es/andresgarci/tclcurl/english What more do you need to do? If this a package, just load into AOLserver4.0 and be done with it. If it isn't, look at it to see how to make it into a tcl package. --Tom Jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] AOLserver4.0 Porting Note
The following information item may be helpful to those who are porting an existing AOLserver installation to AOLserver 4.0. The AOLserver C API functions Ns_CacheCreate Ns_CacheCreateSz in 4.0 now produce a Warning severity log entry if called with an already existing cache name. The Log entry will look somthing like: [28/Mar/2003:13:32:15][23868.1][-main-] Warning: cache: duplicate cache name: shopping In the pre-4.0 AOLserver, these functions accepted this situation silently. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] TCLcurl .. WAS Re: [AOLSERVER] Bug in tclhttp.c
Roger dodger ... I'm just in the light research phase thinking about what I'll need for an upcoming project - doesn't seem like a big deal - it never is :) When I get to that point (or if I have some free time this weekend) I'll post here about how nicely it plays with aolserver. On Fri, 28 Mar 2003, Tom Jackson wrote: Alfred Werner wrote: They claim to be thread safe... There is a TCL wrapper at http://personal1.iddeo.es/andresgarci/tclcurl/english What more do you need to do? If this a package, just load into AOLserver4.0 and be done with it. If it isn't, look at it to see how to make it into a tcl package. --Tom Jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] CGI memory leaks
I know this subject was addressed a while ago but I'm curious to know if there has been any resolution to this. We have setup a linux box running aolserver 3.5 w/ tcl 8.4.2 and have performed the following tests: 1. Running a very simple perl cgi 2. Running an ADP to do the same as the cgi 3. Running an ADP that execs a command We hammered the snot of the aolserver in each case and case 1 above leaked memory (about 2MB a minute at full throtle) - the other two did not leak memory. In the previous thread it was mentioned that perhaps the leaks were related to 'exec' in a multithreaded app. But in this case, execs from tcl did not result in a leak - only those for the CGI processing. Does anyone know what could cause this or what a potential solution is? (Of course long term we will convert all of our cgis to adps, but that will take time - we'd like to switch out the webserver before then). Any information would be most welcome, Thanks, Matthew -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] CGI memory leaks
1. Running a very simple perl cgi Memory leak in the nscgi module? -- C. R. Oldham Director of Technology NCA CASI -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] CGI memory leaks
Hi Matthew, Sounds like a memory leak in nscgi. Can you send me the perl script and your nsd.tcl file? I'll see if I can duplicate the problem, track it down and fix it. thanks, /s. On Friday, March 28, 2003, at 04:57 PM, Matthew Krenzer wrote: I know this subject was addressed a while ago but I'm curious to know if there has been any resolution to this. We have setup a linux box running aolserver 3.5 w/ tcl 8.4.2 and have performed the following tests: 1. Running a very simple perl cgi 2. Running an ADP to do the same as the cgi 3. Running an ADP that execs a command We hammered the snot of the aolserver in each case and case 1 above leaked memory (about 2MB a minute at full throtle) - the other two did not leak memory. In the previous thread it was mentioned that perhaps the leaks were related to 'exec' in a multithreaded app. But in this case, execs from tcl did not result in a leak - only those for the CGI processing. Does anyone know what could cause this or what a potential solution is? (Of course long term we will convert all of our cgis to adps, but that will take time - we'd like to switch out the webserver before then). Any information would be most welcome, Thanks, Matthew -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] TCLcurl .. WAS Re: [AOLSERVER] Bug in tclhttp.c
Alfred, I hope you find it easy. cURL sounds like a nice package, even nicer that someone has created a tcl wrapper. I doubt that we will use it to replace the http server processing in AOLserver, but as a client package (making aolserver the client) it should be very helpful. --Tom Jackson Alfred Werner wrote: Roger dodger ... I'm just in the light research phase thinking about what I'll need for an upcoming project - doesn't seem like a big deal - it never is :) When I get to that point (or if I have some free time this weekend) I'll post here about how nicely it plays with aolserver. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
I believe in Tcl 8.4 that if regexp sees a simple pattern (i.e. one that string match could use), then it will use string match to process it. I am not sure where exactly that takes place, so I am not sure if that's what you are seeing or not. Maybe once Jeff gets back, he would have some input. --brett On Fri, 2003-03-28 at 10:29, Ayan George wrote: Guys, During my lunch break, I wrote a small program to compare the execution of Tcl_StringMatch() (what ns_register_filter uses to match URLs) and Tcl_RegExpExec() (what I propose ns_register_filter should have the option of using). It looks like the regular expression stuff is just as fast (or slow depending on how you look at it) as the Tcl_StringMatch() we currently use. Of course, I haven't tested it very thouroughly. If you are interested in the code I used, it is here: http://www.ayan.net/software/TclReCmp/ I'd like to take a stab at implementing the RE matching for the ns_register_* procedures if that is okay. -ayan On Fri, 28 Mar 2003, Nathan Folkman wrote: Agree. If you want to take a stab at implementing, and can provide a patch, we'll take a look and get it added to the core. Thanks in advance. - Nathan On Friday, March 28, 2003, at 01:17 PM, Tim Moss wrote: That sounds like a good idea. Espcially if you make the default behaviour whatever the current behaviour is. This will ensure backwards compatibility (with no changes to existing code). If you want the extra flexibility the regexp option gives you then you add it to your code and chaneg the expressions accordingly. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- Brett Schwarz [EMAIL PROTECTED] Very Little -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
Why can't we just use POSIX regular expressions for all of the ns_register* procedures? I'd be concerned about REs degrading performance. REs are usually significantly slower than glob matches, and the registered proc matcher will be called a _lot_. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
[AOLSERVER] Getting Machine/OS_user Information
Hello, is there a known way to get the mac address and logged os_username through ns functions??? -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] ns_register_proc
I agree, but maybe we can add a option to the command, similar to what Tcl's switch and lsearch commands do (i.e. -glob -regexp, etc) --brett On Fri, 2003-03-28 at 07:43, Peter M. Jansson wrote: Why can't we just use POSIX regular expressions for all of the ns_register* procedures? I'd be concerned about REs degrading performance. REs are usually significantly slower than glob matches, and the registered proc matcher will be called a _lot_. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/ -- Brett Schwarz [EMAIL PROTECTED] Very Little -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
