Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread Jim Wilcoxson
What would be even better is to just write the code right in the first place so that no error ever happens. (I tried that. I came close.) People make mistakes. Server software should do something reasonable. The problem with just closing the connection is: - the user will get connection

[AOLSERVER] [ aolserver-Patches-500430 ] bug fix for ns_hostbyaddr

2002-01-07 Thread Ms. Source Forge
Patches item #500430, was opened at 2002-01-07 07:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=303152aid=500430group_id=3152 Category: other Group: None Status: Open Resolution: None Priority: 5 Submitted By: patrick o'leary (pjaol) Assigned to:

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread Peter M. Jansson
Yes. I am arguing that the server should always return a 500 if it reaches the end of a connection with no other results. I don't know the technical feasibility of this but it does not seem like correct behavior to return nothing to the user. I think the problem is that a filter can

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread Jim Wilcoxson
Maybe there needs to be a flag in ns_write and friends to indicate that something has been written to the connection. If not, send out a 500 before closing the connection. To me, this seems like a general error condition not specific to filters. I imagine (but don't know for a fact) that there

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread David Walker
Perhaps ns_atclose might fulfill some of your needs. Build a preauth filter with a ns_atclose myproc statement in it and myproc will be executed after everything else just before connection close. On Monday 07 January 2002 11:14 am, you wrote: On 2002.01.07, Jim Wilcoxson [EMAIL PROTECTED]

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread Dossy
On 2002.01.07, David Walker [EMAIL PROTECTED] wrote: Perhaps ns_atclose might fulfill some of your needs. Build a preauth filter with a ns_atclose myproc statement in it and myproc will be executed after everything else just before connection close. Registering a script with ns_atclose won't

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread David Walker
hmm. Under Linux I issued a ns_write command from a procedure called by ns_atclose and the output was appended to the previous ns_write output and displayed in my browser. The docs don't actually specify whether it should take place before or after the connection close. On Monday 07 January

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread Jerry Asher
Totally agree. In fact, I think there may be other cases where AS 3.4 doesn't log Bad Request errors that are internally generated by AS. I have had users do screen shots of Bad Request, yet I can't find them in my logs. Could be stupidity on my part...dunno yet. Jim I can confirm that

Re: [AOLSERVER] And if you thought nsvhr was an inefficient virtual hosting mechanism...

2002-01-07 Thread David Walker
as a chroot alternative it should very good. I'm not aware of any way to access the parent machine from the virtual machine. as a virtual server it might perform well if you give each vmware machine a dedicated partition and load up on memory (if you assign 128mb or whatever to a virtual

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread Dossy
On 2002.01.07, David Walker [EMAIL PROTECTED] wrote: hmm. Under Linux I issued a ns_write command from a procedure called by ns_atclose and the output was appended to the previous ns_write output and displayed in my browser. The docs don't actually specify whether it should take place before

Re: [AOLSERVER] And if you thought nsvhr was an inefficient virtual hosting mechanism...

2002-01-07 Thread Peter M. Jansson
I think a href=http://user-mode-linux.sourceforge.net/;User-Mode Linux (UML)/a is probably the best chroot alternative for Linux. On BSDs, I imagine jail is better. On Monday, January 7, 2002, at 12:57 PM, Jerry Asher wrote: I do wonder how well it might work as a chroot alternative.

[AOLSERVER] Sharing a socket between C and TCL

2002-01-07 Thread Wojciech Kocjan
Hello. I've written a small C based daemon listening on 999 port. It doesn't do much, but I want to move some of the functions from C to TCL. I'm using Ns_SockListenCallback() and have SOCKET to work with. How do I allow Tcl to use this socket? -- WK

Re: [AOLSERVER] Sharing a socket between C and TCL

2002-01-07 Thread Scott Goodwin
If you're creating the socket in your C module using Tcl channels, I think you just need to get the socket id back and use the standard puts, gets and so on. If you aren't using Tcl channels, you'll need to create your own Tcl commands and use them to read/write bytes. See nsopenssl for an

Re: [AOLSERVER] And if you thought nsvhr was an inefficient virtual hosting mechanism...

2002-01-07 Thread Wojciech Kocjan
This is a small ab test on VMware 3.0 on Windows on P3/850 and a P3/600: Server Software:AOLserver/3.4 -- this is the P3/600 Server Hostname:www.zoro.tcl.pl Server Port:80 Document Path: /ab/ab.adp Document Length:12 bytes Concurrency Level:

[AOLSERVER] Ns_SetCreate is thread safe?

2002-01-07 Thread Andrew Piskorski
Folks, with AOLserver 3.3+ad13 on Solaris (SunOS 5.*), in my own loadable module, I have a Tcl command implemented in C that creates a new ns_set and then does stuff with it, pretty much like this: setPtr = Ns_SetCreate(TclReceiveDataCmd); /* Do more C stuff - stick data into the set, etc.

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread Dave Siktberg
The OpenACS system implements a filter manager, ad_register_filter, that sits on top of ns_register_filter and lets you set a priority number for each filter you register with it. The master filter (registered with ns_register_filter) applies each registered filter in turn in the order you

Re: [AOLSERVER] Critical filter failed

2002-01-07 Thread Dossy
On 2002.01.07, Dave Siktberg [EMAIL PROTECTED] wrote: You could use such a feature to force the order of trace filters. Perhaps that would address your need. I already said that trace filters aren't what I need. Trace filters are executed too late. Unless I'm wrong. My testing a while back

Re: [AOLSERVER] Ns_SetCreate is thread safe?

2002-01-07 Thread Rob Mayoff
+-- On Jan 7, Andrew Piskorski said: Problem is, I'm sometimes getting a segfault during the malloc in the Ns_SetCreate (see below), and I don't understand why. Could someone give me advice on this, please? Thanks! Program received signal SIGSEGV, Segmentation fault.

Re: [AOLSERVER] Ns_SetCreate is thread safe?

2002-01-07 Thread Andrew Piskorski
On Mon, Jan 07, 2002 at 02:42:14PM -0600, Rob Mayoff wrote: Looks like heap corruption. You are probably writing past the end of a block, or writing to a freed block, or freeing a block twice some time before this call. Eeps. Any suggestions on how best to track down where in my code I'm