[AOLSERVER] ns_vhr command not working from a .tcl script for me
hi, ns_vhr command is not working for me, when it is embedded in .tcl script the server is responding with error something like invalid command name ns_vhr update .. but when i tried it with nscp it is working . is it restricted for server control port admin .. what changes shall i make to my tcl script to work Madhu Sudhana Rao azri _ Cricket World Cup 2003- News, Views and Match Reports. http://server1.msn.co.in/msnspecials/worldcup03/ I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] virtual hosting options and a fantasy ....
It concerns me seriously when virtual hosting was at one time supported, then taken out, now being put back in by the volunteer society. Once I implement a solution, I need to know that certain necessary features aren't going to go away leaving me without a work-a-round. Why would the AOL team think so selfishly by removing virtual hosting? Do they not care that others rely on their server? -- ed __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] virtual hosting options and a fantasy ....
Edward Wilson said: Why would the AOL team think so selfishly by removing virtual hosting? Do they not care that others rely on their server? You are quite passionate about this, aren't you? ;-) Although there was virtual serving in 2.3, it was not hostname based. Personaly, I find that instead of putting extra directives in one config file, moving them to different config files and having some more lines in my start-up scripts not really a big deal and certainly not something that significantly breaks moving code from 2.3 to 3.0. The trade off is worth it considering how much more lean and mean 3+ is! As an added bonus you get a completely seperate environment! I don't find AOL selfish at all for making any changes, they build a kick-ass server for themselves and share it with the world, thank you very much. They will not make application breaking changes because they are their own major client and don't want to break their own apps. Looking at the track record, maintaining almost 100% code compatibility from 1995 to 2003 (dispite architecture changes) is unheard of in the world of web application servers! Bas. PS: You are perfectly welcome to still run 2.3 if you want to! ;-) I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] virtual hosting options and a fantasy ....
We're trying! ;-) Virtual server and Win32 support are two good examples of our renewed commitment to trying to better balance internal needs and requirements with those of the Community at large. It's not always going to be perfect, and we won't always be able to satisfy everyone, but we are committed to maintaining a more open dialogue with everyone. Thanks to everyone who has stuck with us over the years, and who continue to help us improve the server. - Nathan On Wednesday, March 5, 2003, at 10:53 AM, Daniel P. Stasinski wrote: With the core team in place, development emphasis is now based on both the needs of AOL as well as those of the community. With that, needed features are being re-implemented. I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] ns_vhr command not working from a .tcl script for me
madhusudhanarao sunkara wrote: hi, ns_vhr command is not working for me, when it is embedded in .tcl script the server is responding with error something like invalid command name ns_vhr update .. but when i tried it with nscp it is working . is it restricted for server control port admin .. what changes shall i make to my tcl script to work This is surprising to me, but then I am not sure I ever used it from anything other than the nscp command line. I love the nscp command line. (Back when I was a kid, we had to wget | cat all of our web pages.) I haven't looked at this code in more than a year, and, I am trying not to use it now in fact. I don't have time to look at it now. A first glance at the code itself, and I don't see anything that should restrict it to just the control port. Also, invalid command does not appear in the code, although unknown command does. Best of luck, I am interested in knowing what you find out. Jerry I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] virtual hosting options and a fantasy ....
From: Edward Wilson [EMAIL PROTECTED] Once I implement a solution, I need to know that certain necessary features aren't going to go away leaving me without a work-a-round. You may want to investigate alternatives to getting free software from a public server or cvs. Some alternatives include: 1. purchasing a server - but then, you still don't have the certainty that you require I guess. 2. purchasing support - then at least you could work with someone to reimplement features that are missing 3. freeze at a particular version of the software that meets your needs, and just live with bugs and without new features, or even attempt to 'back port' fixes and features to your frozen version yourself. 4. write your own server. 3 of the 4 can give you the assurances you need. -- Tcl - The glue of a new generation. URL: http://wiki.tcl.tk/ Larry W. Virden mailto:[EMAIL PROTECTED] URL: http://www.purl.org/NET/lvirden/ Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -- I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] virtual hosting options and a fantasy ....
Edward Wilson wrote: Why would the AOL team think so selfishly by removing virtual hosting? Do they not care that others rely on their server? Nothing was lost in removing virtual hosting, except the difficulty of mantaining a single config file for all those hosts. Since each server takes up as much memory running separately as when combined, resources are not saved. This is very different from Apache which could easily run thousands of virtual hosts without increasing memory useage (since is spawned a new process for each request anyway). With the style of virtual hosting in the pre 3.0 series, any change to a virtual server would require a restart of the entire process, bringing down every virtual host in the process. Since each virtual server was initialized separately, the time to restart was proportional to the number of virtual servers. I don't know what the current situation is with the new implimentation, but if it is the same, I can't see why it would be useful. I believe the config file problems are greatly reduced. In the mean time several users, including myself, developed virtual hosting using registered filters. This proved to be very efficient, even when written in tcl. --Tom Jackson I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
[AOLSERVER] nsopenssl 2.1 allergic to RedHat 8.0?
I updated one of my systems to RH 8.0, and then updated OpenSSL to 0.9.7, and now I'm having trouble compiling nsopenssl 2.1 from the tarball on ScottG's site. Anyone else have similar troubles? I'm digging in to try to figure it out, but I thought I'd ask the crew, in case someone else has an answer. One difference is that OpenSSL 0.9.6 appears to define a symbol THREADS to indicate that OpenSSL was built for threads, while OpenSSL 0.9.7 defines OPENSSL_THREADS, but that's easy enough to fix. I'm guessing most of my troubles are coming from a newer gcc being a little more pedantic (which I didn't think was possible). Thanks, Pete. I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] nsopenssl 2.1 allergic to RedHat 8.0?
John Caruso pointed this out a couple of weeks ago. Read below: From: John Caruso [EMAIL PROTECTED] Date: Fri Feb 21, 2003 5:57:14 PM US/Central To: [EMAIL PROTECTED] Subject: Test for THREADS in thread.c (in nsopenssl 2.1) I'm in the process of (re)building nsopenssl 2.1 using openssl 0.9.7a, and I ran into one problem. In thread.c there's the following test: #ifndef THREADS #error OpenSSL was not compiled with thread support! #endif But it appears that in openssl 0.9.7a the macro name is now OPENSSL_THREADS, not THREADS (and they also don't reference OPENSSL_THREAD_DEFINES anymore to determine whether or not to set this--it's set unconditionally). I checked the nsopenssl 2.2beta7 tarball and it looks like it hasn't been updated to reflect the changed macro name either. I got around it by defining CFLAGS=-DTHREADS before the compilation, but long-term I'm assuming you'll want to change this in the code. - John On Wednesday, March 5, 2003, at 04:27 PM, Peter M. Jansson wrote: I updated one of my systems to RH 8.0, and then updated OpenSSL to 0.9.7, and now I'm having trouble compiling nsopenssl 2.1 from the tarball on ScottG's site. Anyone else have similar troubles? I'm digging in to try to figure it out, but I thought I'd ask the crew, in case someone else has an answer. One difference is that OpenSSL 0.9.6 appears to define a symbol THREADS to indicate that OpenSSL was built for threads, while OpenSSL 0.9.7 defines OPENSSL_THREADS, but that's easy enough to fix. I'm guessing most of my troubles are coming from a newer gcc being a little more pedantic (which I didn't think was possible). Thanks, Pete. I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/ I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] virtual hosting options and a fantasy ....
On 2003.03.05, Jeff Hobbs [EMAIL PROTECTED] wrote: And I would be glad to provide you full aolserver support with customizations for the small sum of raise_pinkyone mellion dollars/raise_pinky. ;^) Uh, sir, Vignette Corporation already makes a Tcl-enabled application server for several million dollars already. /me waits for the raisePinkyone HUNDRED melion dollars/raisePinky response. -- 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) I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] virtual hosting options and a fantasy ....
Sorry, I didn't mean to offend the Aol server Team; I do thank them for their generosity. I misunderstood something I read--sorry once again. Thank you everyone for not flaming me off-line. Best wishes to all! -- ed __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] AS 4.0 (beta 2) running on privledge port
On Wednesday, March 5, 2003, at 07:20 PM, Brett Schwarz wrote: However, NsPreBind does nothing is the -b or -B option are not given, when, I believe it should pre bind anyways from what is given in the config file. I could be wrong here. My inittab line: ww:345:respawn:/usr/local/aolserver-4.0/bin/nsd -i -b 192.168.1.239:80 -u web -g web -t /usr/local/aolserver-4.0/click.tcl You must specify the -b on the command line, It does work. I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
[AOLSERVER] ANNOUNCE: DNS Module
Some time ago somebody mentioned(sorry i did not save the message, do not remember the name) about DNS module for AOLserver, it happened i implemented DNS server before for another project so i figured i can quickly write simple DNS server module. Actually it was fun for the last couple days after writing mostly Web applications to do something low-level in C. So, the first version of nsdns module is released. Briefly it is simple server and DNS proxy in one, it serves it own records and forwards everything else to remote DNs server. All replies are cached locally. That's basically it. To download: ftp://ftp.crystalballinc.com/pub/vlad/nsdns.tar.gz I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
