On 5/29/09 1:27 PM, Jade Rubick wrote:
Personally, even though I think many in the community don't like Dossy
acting without community involvement, I'd rather see something done than
nothing, as long as it isn't harming the project.
I definitely understand that people dislike my approach. I
Hi Dossy,
To be frank, the only reason why I keep using the Trac ticket tracker
is that it's the one I found. Had I known that the sourceforge ticket
tracker was the active one, I would have used that one instead. Begs
to question though... why two ticket trackers?
Anyway, thanks everyone for
On 5/20/09 11:11 AM, Jim Davidson wrote:
Yup -- agreed. I was talking with Dossy who says the Trac stuff is
generally out of date anyway, the definitive bug list is still on
Sourceforge (definitive in it's the place, can't say how accurate the
bug reports are).
I would love to hear that the
I also checked on the other ticket I mentioned on the commit logs and
it seems that the ticket may have been addressed with aolserver 4.5
too... so I think it's looking like everything is resolved.
On May 20, 11:11 pm, Jim Davidson jgdavid...@mac.com wrote:
Yup -- agreed. I was talking with
Tom Jackson schrieb:
On Thu, 2009-05-14 at 18:08 -0400, Jim Davidson wrote:
Good idea. Maybe it would make sense to disable it by default with
some config flag to enable?
I was thinking the same, but I wasn't sure how many people actually use
this command.
i would even
One thing which would be nice is to put the Tcl API into a module which
as to be loaded, and keep the C API available in the core. It is
obviously more work, but the admin has to make a choice to load the Tcl
API, which is more open to misuse. I did something like this for a few
additional ns_conn
Hi,
I'm looking at the head code and it appears it's now safe -- the
connection list is walked with a pool lock held and the request data
(method, url) seem to be copied with a global reqlock mutex held.
Jade: What version of AOLserver are you using?
-Jim
On May 15, 2009, at 10:06
I guess if it's thread safe now, the ticket should be closed with a
reference to aolserver 4.5.
2009/5/16 Jim Davidson jgdavid...@mac.com
Hi,
I'm looking at the head code and it appears it's now safe -- the connection
list is walked with a pool lock held and the request data (method, url)
Hi,
I'm trying to debug an AOLserver crash and the point of crash seems to
be AppendConn in NS_GetProcInfo... I will post the stack trace after
just for reference.
Looking through the ticket tracker on AOLserver, I found two tickets
of particular interest:
Hi,
Do you have some sort of background job that calls ns_server
active (or similar) regularly? That could lead to random crashes.
The description in http://dev.aolserver.com/trac/ticket/152 is
accurate: The code, by design, is not strictly safe as it's assumed
to only be used
Ironically, we have some monitoring code that does use that functionality.
So our monitoring is killing our servers. Nice!
I'm removing that code now.
Jade Rubick
Director of Development
TRUiST
120 Wall Street, 4th Floor
New York, NY USA
jrub...@truist.com
+1 503 285 4963
+1 707 671 1333 fax
Yup -- should really have been documented better -- sorry about that.
Anyway, what is the monitoring attempting to dig up? There may some
other safe ways to get the same.
-Jim
On May 14, 2009, at 2:04 PM, Jade Rubick wrote:
Ironically, we have some monitoring code that does use that
I'm just happy we figured it out.
We were using this call:
set connections [ns_server active]
But it wasn't in a scheduled proc, so I just moved it behind a
password protection section, and put a warning around it. We seldom
(never) used that page anyway. I think a bot may have found it or
Maybe calling the API should result in a ns_log Warning to indicate a
potential crash.
tom jackson
On Thu, 2009-05-14 at 13:26 -0700, Jade Rubick wrote:
I'm just happy we figured it out.
We were using this call:
set connections [ns_server active]
But it wasn't in a scheduled
Good idea. Maybe it would make sense to disable it by default with
some config flag to enable?
Jim
Sent from my iPhone
On May 14, 2009, at 4:49 PM, Tom Jackson t...@rmadilo.com wrote:
Maybe calling the API should result in a ns_log Warning to indicate a
potential crash.
tom jackson
On
On Thu, 2009-05-14 at 18:08 -0400, Jim Davidson wrote:
Good idea. Maybe it would make sense to disable it by default with
some config flag to enable?
I was thinking the same, but I wasn't sure how many people actually use
this command.
This must be one of a very few commands that I have
How about having the proc enable only if debug settings are turned on
on AOLserver?
On May 15, 6:08 am, Jim Davidson jgdavid...@mac.com wrote:
Good idea. Maybe it would make sense to disable it by default with
some config flag to enable?
Jim
Sent from my iPhone
On May 14, 2009, at 4:49
17 matches
Mail list logo
