Am 10.07.2006 um 20:34 schrieb Stephen Deasey:
Limits will save the day, and cure world
hunger...
... and win the next world football cup in South Africa
in four years :-)
Cheers,
Zoran
right
Stephen Deasey wrote:
On 7/10/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
This is from AS 3.3.1
typedef enum {
Ns_DrvIdName,
Ns_DrvIdStart,
Ns_DrvIdAccept,
Ns_DrvIdStop,
Ns_DrvIdInit,
Ns_DrvIdRead,
Ns_DrvIdWrite,
Ns_DrvIdClose,
Ns_DrvIdFree,
On 7/10/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
This is from AS 3.3.1
typedef enum {
Ns_DrvIdName,
Ns_DrvIdStart,
Ns_DrvIdAccept,
Ns_DrvIdStop,
Ns_DrvIdInit,
Ns_DrvIdRead,
Ns_DrvIdWrite,
Ns_DrvIdClose,
Ns_DrvIdFree,
Ns_DrvIdPeer,
Ns_Drv
This is from AS 3.3.1
typedef enum {
Ns_DrvIdName,
Ns_DrvIdStart,
Ns_DrvIdAccept,
Ns_DrvIdStop,
Ns_DrvIdInit,
Ns_DrvIdRead,
Ns_DrvIdWrite,
Ns_DrvIdClose,
Ns_DrvIdFree,
Ns_DrvIdPeer,
Ns_DrvIdLocation,
Ns_DrvIdHost,
Ns_DrvIdPort,
Ns_DrvIdSendF
On 7/10/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
i agree, driver interface in the 3.x days was much better and flexible,
i was using it and tried to hack 4.x since then.
It's not bad if all you want to do is Send/Revc, but it seems we
don't. Let's come up with a plan for what functions we
i agree, driver interface in the 3.x days was much better and flexible,
i was using it and tried to hack 4.x since then.
Stephen Deasey wrote:
On 7/10/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
NS_FATAL in context of these functions means unrecoverable error, but if
name is not very good it
On 7/10/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
NS_FATAL in context of these functions means unrecoverable error, but if
name is not very good it can be changed
Here's some code checking for NS_FATAL and recovering...
if (status == NS_FATAL || sockPtr->reqPtr == NULL || !SetServer(sock
NS_FATAL in context of these functions means unrecoverable error, but if
name is not very good it can be changed
Stephen Deasey wrote:
NS_FATAL doesn't make any sense. Fatal means unrecoverable error, as
in Ns_Fatal(...): and the server exits.
Anyway, the following two disagree. Whether they
NS_FATAL doesn't make any sense. Fatal means unrecoverable error, as
in Ns_Fatal(...): and the server exits.
Anyway, the following two disagree. Whether they intend "request
cannot be parsed" or "driver function not supported", NS_FATAL isn't
the way to say it.
/*
*---
This crashes most of the time to me:
#0 0x00539d34 in NsWriterQueue (conn=0x9507838, nsend=2048,
chan=0x96af320, fp=0x0, fd=-1, data=0x0) at driver.c:2927
2927Ns_Log(Notice, "Writer: %d: started sock=%d, fd=%d:
size=%u, flags=%X: %s",
(gdb) bt
#0 0x00539d34 in NsWriterQueue (conn=0x9507
On 7/10/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Am 10.07.2006 um 15:49 schrieb Zoran Vasiljevic:
>
> As the subject says, I'm mostly ns_confused.
... and tired... Just forget about that. The thing
is I should have tested from two threads at the
same time...
Uhhh
Don't
On 7/10/06, Rick Cobb <[EMAIL PROTECTED]> wrote:
We do something fairly strange on our commands that might be useful
here. We treat the string argument for a duration or timer as having 3
potential signs: "-", "+", and "@". Dash and plus *always* mean
relative-to-now. @ always means absolute t
We do something fairly strange on our commands that might be useful
here. We treat the string argument for a duration or timer as having 3
potential signs: "-", "+", and "@". Dash and plus *always* mean
relative-to-now. @ always means absolute time.
Any given option or argument documents whethe
Am 10.07.2006 um 16:56 schrieb Zoran Vasiljevic:
Am 10.07.2006 um 16:44 schrieb Vlad Seryakov:
I use 8.4.13 and AOLserver mentions on 4.5 release that 8.4.13 is the
right version.
Well, no...
Reading symbols for shared libraries .++ done
[10/Jul/2006:16:55:09][23983.2684415384][-main-] No
Am 10.07.2006 um 16:44 schrieb Vlad Seryakov:
I use 8.4.13 and AOLserver mentions on 4.5 release that 8.4.13 is the
right version.
Well, no...
Reading symbols for shared libraries .++ done
[10/Jul/2006:16:55:09][23983.2684415384][-main-] Notice: binder: started
[10/Jul/2006:16:55:10][23983.2
I use 8.4.13 and AOLserver mentions on 4.5 release that 8.4.13 is the
right version.
Zoran Vasiljevic wrote:
Am 10.07.2006 um 16:31 schrieb Vlad Seryakov:
That is strange, what version of Tcl is it?
[10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:
NaviServer/4.99.2 startin
Am 10.07.2006 um 16:31 schrieb Vlad Seryakov:
That is strange, what version of Tcl is it?
[10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:
NaviServer/4.99.2 starting
[10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:
security info: uid=0, euid=0, gid=0, egid=
That is strange, what version of Tcl is it?
Zoran Vasiljevic wrote:
Am 10.07.2006 um 16:25 schrieb Vlad Seryakov:
Does it happen all the time
Every time I stop the server. Just did a fresh checkout and
recompile:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_
Am 10.07.2006 um 16:25 schrieb Vlad Seryakov:
Does it happen all the time
Every time I stop the server. Just did a fresh checkout and
recompile:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x0004
[Switching to process 23748
Does it happen all the time, i am running new code for several days now
and do frequent shutdown, never crashed.
Zoran Vasiljevic wrote:
[10/Jul/2006:16:19:02][23692.25176064][-sched-] Notice: sched:
shutdown complete
[10/Jul/2006:16:19:02][23692.25171456][-socks-] Notice: socks:
shutdown pe
[10/Jul/2006:16:19:02][23692.25176064][-sched-] Notice: sched:
shutdown complete
[10/Jul/2006:16:19:02][23692.25171456][-socks-] Notice: socks:
shutdown pending
[10/Jul/2006:16:19:02][23692.25171456][-socks-] Notice: nscp: shutdown
[10/Jul/2006:16:19:02][23692.25171456][-socks-] Notice: socks:
Am 10.07.2006 um 15:49 schrieb Zoran Vasiljevic:
As the subject says, I'm mostly ns_confused.
... and tired... Just forget about that. The thing
is I should have tested from two threads at the
same time...
Uhhh
Zoran
Hi!
As the subject says, I'm mostly ns_confused.
server1:nscp 5> ns_cache_create some 4096
server1:nscp 6> ns_cache_eval -timeout 5 some key {after 1; set a
13}
13
server1:nscp 8> ns_cache_create other 4096
server1:nscp 9> ns_cache_eval -timeout [expr {[clock seconds] + 5}]
other key {a
23 matches
Mail list logo
