[AOLSERVER] [ aolserver-Patches-509413 ] Patch for -g option
Patches item #509413, was opened at 2002-01-27 20:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=303152aid=509413group_id=3152 Category: other Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Griffin (tresero) Assigned to: Nobody/Anonymous (nobody) Summary: Patch for -g option Initial Comment: Fixes bad uid/gid parsing in nsmain. Now it acutally works. -- Comment By: Kriston Rehberg (kriston) Date: 2002-01-28 07:13 Message: Logged In: YES user_id=16427 On which platforms does this fail? Do you use the z option while starting up? We have been using -g and -u forever on Solaris, SGI, and some other platforms and it works. Thanks, Kris -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=303152aid=509413group_id=3152
[AOLSERVER] [ aolserver-Patches-509413 ] Patch for -g option
Patches item #509413, was opened at 2002-01-27 20:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=303152aid=509413group_id=3152 Category: other Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Griffin (tresero) Assigned to: Nobody/Anonymous (nobody) Summary: Patch for -g option Initial Comment: Fixes bad uid/gid parsing in nsmain. Now it acutally works. -- Comment By: Kriston Rehberg (kriston) Date: 2002-01-28 07:13 Message: Logged In: YES user_id=16427 On which platforms does this fail? Do you use the z option while starting up? We have been using -g and -u forever on Solaris, SGI, and some other platforms and it works. Thanks, Kris -- Comment By: Kriston Rehberg (kriston) Date: 2002-01-28 07:13 Message: Logged In: YES user_id=16427 On which platforms does this fail? Do you use the z option while starting up? We have been using -g and -u forever on Solaris, SGI, and some other platforms and it works. Thanks, Kris -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=303152aid=509413group_id=3152
Re: [AOLSERVER] Ns_Pool: invalid block
- Original Message - From: Kriston Rehberg [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 28, 2002 8:20 AM Subject: Re: [AOLSERVER] Ns_Pool: invalid block Nearly always when we encounter this error it's due to memory being overwritten by other code or due to a blown thread stack. Nearly always we can find the error by doing one of the following: 1) Start with -z option to turn on the zippy memory allocator which has a simple out-of-bounds checker. A good litmus test is to run without -z and then with -z and see which one fails more quickly (should be the -z one that fails quickly). The really fun part with the -z option is I can sometimes get it to work and then out of the blue it stops working with no warning and no logged errors.. I gave up trying to demonstrate the failure and gave up trying to use it.. sigh.. -- Patrick Spence, MIS Mayor Pharmaceutical Labs/Regency Medical Research, Ltd. 2401 South 24th Street, Phoenix, AZ 85034 [EMAIL PROTECTED] - http://www.vitamist.com *** All contents of this email message are confidential and private. Please do not forward to anyone that this message is not intended for without permission. If you have received this email in error, please contact the sender and then delete all copies of the message that you have. Thank you. ***
[AOLSERVER] Bugs in ns_dbquotevalue
Hello.
Here is what caused problems for me with both mySQL and PostgreSQL:
ns_dblist $h "SELECT lower([ns_dbquotevalue {ABC'DEF\'}])"
Basically it quoted the string into 'ABC''DEF\'', which is not correct.
Also, it does not work correctly for UTF-escapable characters.
proc ns_dbquotevalue {val} {
set val [string map [list "'" "''" "\\" ""] $val]
return "'$val'"
}
Here's the code I used - it does not handle datatypes, but I never used
them anyway :)
Any comments on this one?
--
WK
Re: [AOLSERVER] Bugs in ns_dbquotevalue
I've also noticed this problem. It can be exploited to execute functions in
your database in certain circumstances where you're quoting submitted data.
I think this function may need different behavior for Oracle or Postgres.
On Monday 28 January 2002 11:46 am, you wrote:
Hello.
Here is what caused problems for me with both mySQL and PostgreSQL:
ns_dblist $h "SELECT lower([ns_dbquotevalue {ABC'DEF\'}])"
Basically it quoted the string into 'ABC''DEF\'', which is not correct.
Also, it does not work correctly for UTF-escapable characters.
proc ns_dbquotevalue {val} {
set val [string map [list "'" "''" "\\" ""] $val]
return "'$val'"
}
Here's the code I used - it does not handle datatypes, but I never used
them anyway :)
Any comments on this one?
Re: [AOLSERVER] Sun and Solaris vs. Intel and Linux
Nothing formal here, but while debugging a performance issue with the Sybase driver, I had a Sun E250 with 2 400MHz CPUs and 1GB RAM, and one generic Linux box with a 700MHz PIII and 512MB RAM. Both systems ran AOLserver 3.x; the Linux box ran a Sybase server using the Sybase 11.x server available for free from Sybase, while the Sun had an external Sybase server which was housed on an unknown machine (probably a mid-range SGI or HP box). The Linux box was able to query rows from the database approximately 4x faster than the Sun was, but it's possible the difference was network chatter between the Sun and its Sybase server or other causes. (Both systems used the local version of the Sybase proxy interface, so that wasn't the problem.) This was an isolated, artificial test, meant solely to get a bead on row fetch performance in the Sybase driver, and does not necessarily reflect overall performance, nor how gracefully the systems fail. It sure was interesting, though, to see such a wide margin of performance between the two systems. One of the biggest issues in a serious production environment is that Sun will sell you a reasonably-priced service contract where you can call them as much as you like for issues, with no time limits on each issue, and no limit on the number of issues. You can't buy such contracts for Linux. Linuxcare is a popular Linux service vendor, and their plans basically boil down to $200/hour support unless you lean on them, and then the price will drop some, but you still face issue/time-per-issue limits. The Sun contract covers both hardware and software issues. It's possible to rationalize the Linux support situation by saying that, for the price, you can buy spares, and the Linux community is fairly good (although sometimes it can be harsh to poorly-phrased questions) at providing software support. I have a customer who won't consider Linux in production because he can't get all-you-can-eat support contracts for Linux. If this is important to you, it's worth consideration.
