[AOLSERVER] script loading sequence

Hi! I have a question about how to load at startup scripts in few different files in certain sequence. Is there some precedence of it or need I take care by myself? Thanks in advance Remigiusz -- ---/\--

Re: [AOLSERVER] Filtering logs

The thought never occurred to us that logging on a production server would be so extensive that it would require such filtering by severity. Usually production servers should only spew out the most interesting messages: Warning, Error and Fatal. If you're routinely logging on a production

Re: [AOLSERVER] Filtering logs

Another option is to preface important log messages with a particular string. For example, I use ERROR - some message and EXCEPTION - some message for logging - old habit. thomas -Original Message- From: Kriston Rehberg [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001

Re: [AOLSERVER] Filtering logs

My own experience is that logging is essential, even in production. We log everything - SQL commands, debug logs we've inserted... everything. The problem is that when a customer writes in and says I can't login to your web site, without logs you are left with telling them clear your cache and

Re: [AOLSERVER] Detecting Aborted Connections

G'Day, Is there any way to find out if the connection was aborted eg the user pressed the stop button or somehow the connection got broken. Currently one finds that the script continues on relentessly. This scenario is important where 1) Tunneling XMLRPC calls. To the client a non-return value

[AOLSERVER] How do I not make a patch too big?

I'm trying to bring the nsvhr/nsunix patches up to speed with AOLserver 3.3 and 3.4 and eventually AOLserver 4.0. It's a pretty big group of changes: some core issues were fixed in nsd/drv.c, nsunix/nsunix.c, nsvhr/nsvhr.c, and nssock/sock.cpp. These changes take what's broken and fix it.

Re: [AOLSERVER] Detecting Aborted Connections

Is there any way to find out if the connection was aborted eg the user pressed the stop button or somehow the connection got broken. Currently one finds that the script continues on relentessly. If you use ns_write, you can check its return value. As I recall, it returns 0 on failure and 1

Re: [AOLSERVER] How do I not make a patch too big?

On 2001.07.18, Jerry Asher [EMAIL PROTECTED] wrote: Is there some magical technical solution? How do other developers or projects handle such things? (Please no comments about not making big/broad patches in the future. Sometimes, it just doesn't seem possible to take big additions of

[AOLSERVER] -s server flag: aolserver 3.3 experience

I apologize if this is a resend Late last night when my brain may have been working at only 3%, I upgraded from ad12 to ad13, by downloading the source and building (on red hat linux). Upon installation, I ran aolserver, using the sample-config.tcl file. That worked fine. So I killed the

[AOLSERVER] [ aolserver-Bugs-442600 ] ns_info server is broken

Bugs item #442600, was opened at 2001-07-18 15:13 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=103152aid=442600group_id=3152 Category: Configuration: Server Group: aolserver3_3 Status: Open Resolution: None Priority: 5 Submitted By: Jerry Asher (jerryasher)

Re: [AOLSERVER] -s server flag: aolserver 3.3 experience

On 2001.07.18, Jerry Asher [EMAIL PROTECTED] wrote: When I restarted the server none of this worked, and my 3am debugging seems to reveal that the value of [ns_info server] is at the time the config file is evaluated. Does this happen in 3.4? - Dossy -- Dossy Shiobara