On 16.09.2006, at 06:40, Ibrahim Tannir wrote:
So a porting guide is is becoming necessary (?).
Perhaps... but at this point we have no need for that, yet.
I just wanted to stress that such thing will be inevitable
in the future.
So a porting guide is is becoming necessary (?).
-Ibrahim
Unrelatred:
We are now pretty much drifting away in terms of functionality
and API from our sister project, but nothing is for free. I guess
we are pretty different in other areas so people eventually moving
to our platform will have qui
On 14.09.2006, at 22:30, Vlad Seryakov wrote:
yes,per pool is safer
Allright. All is done and checked in. The ns_proxy.man is
also updated accordingly.
Unrelatred:
We are now pretty much drifting away in terms of functionality
and API from our sister project, but nothing is for free. I guess
On 15.09.2006, at 08:23, Gustaf Neumann wrote:
On a power5+ with linux and gcc, int stays at 32bit even with 64bit
code.
Yes, this is what I also read everywhere. The int should stay 32bit
even on 64bit boxes otherwise the porting effort might be a
nightmare for just about everybody.
On a power5+ with linux and gcc, int stays at 32bit even with 64bit code.
-gustaf
--- default compilation
% cc t.c -o t
% file t
t: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV),
for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped
% ./
yes,per pool is safer
Zoran Vasiljevic wrote:
On 14.09.2006, at 22:13, Vlad Seryakov wrote:
New command will be better and more clear
OK.
ns_proxy stop ?pool? ?handle?
The [ns_proxy stop] will stop all running proxies (brrr.. )
and [ns_proxy stop pool] only those belonging to a pool
and
On 14.09.2006, at 22:13, Vlad Seryakov wrote:
New command will be better and more clear
OK.
ns_proxy stop ?pool? ?handle?
The [ns_proxy stop] will stop all running proxies (brrr.. )
and [ns_proxy stop pool] only those belonging to a pool
and [ns_proxy stop pool handle] only that particula
On 14.09.2006, at 22:13, Stephen Deasey wrote:
Oh, OK. So on an AMD64 box, pointers are 64bit, but int's are 32?
You need long int to get 64bit?
Yes. Normally (what is normal today?) on a 64 bit box/compiler:
int = 32
ptr = 64
long long = 64
long = 64 (this I'm not sure)
short = 16
On 14.09.2006, at 22:10, Stephen Deasey wrote:
But now the initiating thread is tied up with an idle wait -- i.e. you
can't intiate the job and have it run in the background. This
issolates the code externaly, but it requires resources (a thread) for
each job you start.
The ns_job command c
New command will be better and more clear
Zoran Vasiljevic wrote:
On 14.09.2006, at 20:12, Zoran Vasiljevic wrote:
A list of poolId/script. If we would expand the
[ns_proxy clear ?pool?]
to be
[ns_proxy clear ?pool ?handle??]
then you'd be able to:
ns_proxy clear pool pool-7
AHHH! Help
On 9/14/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
On 14.09.2006, at 21:52, Stephen Deasey wrote:
>
>
> This code looks wrong:
>
> /*
>* It is pain in the neck to get a satisfactory definition of
>* u_int_XX_t or uintXX_t as different OS'es do that in different
>* header file
On 9/14/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
On 14.09.2006, at 21:46, Stephen Deasey wrote:
> What are your rules for checking for a long running process?
>
> If the ns_proxy command is for isolating badly behaved code, it seems
> to me there could usefully be a few more built in che
On 14.09.2006, at 20:12, Zoran Vasiljevic wrote:
A list of poolId/script. If we would expand the
[ns_proxy clear ?pool?]
to be
[ns_proxy clear ?pool ?handle??]
then you'd be able to:
ns_proxy clear pool pool-7
AHHH! Help!
The [ns_proxy clear] actually clears proxies which
are left in
On 14.09.2006, at 21:52, Stephen Deasey wrote:
This code looks wrong:
/*
* It is pain in the neck to get a satisfactory definition of
* u_int_XX_t or uintXX_t as different OS'es do that in different
* header files and sometimes even do not define such types at all.
* We choose
On 14.09.2006, at 21:46, Stephen Deasey wrote:
What are your rules for checking for a long running process?
If the ns_proxy command is for isolating badly behaved code, it seems
to me there could usefully be a few more built in checks for bad
behaviour, rather than having to implement these ch
On 9/14/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Hi!
Motivated by the Vlad's recent report, I took another
tour arround the code and did yet-another cleanup phase.
Amazing howmany things you can find when you revisit the
code after some time...
I have fixed numerous MT-safeness problems,
What are your rules for checking for a long running process?
If the ns_proxy command is for isolating badly behaved code, it seems
to me there could usefully be a few more built in checks for bad
behaviour, rather than having to implement these checks manually.
For example, how about a switch wh
then the case is closed (for me), once ready i will use it
Zoran Vasiljevic wrote:
On 14.09.2006, at 20:25, Vlad Seryakov wrote:
Yes, this looks good, can you put pid there as well?
yes.
-
Using Tomcat but need to do mo
On 14.09.2006, at 20:25, Vlad Seryakov wrote:
Yes, this looks good, can you put pid there as well?
yes.
Yes, this looks good, can you put pid there as well?
Zoran Vasiljevic wrote:
On 14.09.2006, at 20:12, Zoran Vasiljevic wrote:
server1:nscp 7> ns_proxy active pool
pool-7 {exec sleep 1}
Alternatively, we can change the return value
of the command to be:
{proxyId timestamp script} {pro
On 14.09.2006, at 20:12, Zoran Vasiljevic wrote:
server1:nscp 7> ns_proxy active pool
pool-7 {exec sleep 1}
Alternatively, we can change the return value
of the command to be:
{proxyId timestamp script} {proxyId timestamp script} ...
i.e. a list of lists, where each sublist has variab
Thanks, no hurry
Zoran Vasiljevic wrote:
On 14.09.2006, at 20:13, Vlad Seryakov wrote:
That is what i need
I was afraid of you saying this!
Because I had that code already done and then
have removed it because I believed nobody would
use it anyway
Allright, if you want (and I see no rea
On 14.09.2006, at 20:13, Vlad Seryakov wrote:
That is what i need
I was afraid of you saying this!
Because I had that code already done and then
have removed it because I believed nobody would
use it anyway
Allright, if you want (and I see no reasons why not)
I can plug that in again. To
That is what i need
Zoran Vasiljevic wrote:
On 14.09.2006, at 20:03, Vlad Seryakov wrote:
Can i do this from other thread, spawn in one and check in another,
actually this is what i need. I can have multiple processes running,
then according to some rules i will check which one is taking too l
On 14.09.2006, at 20:03, Vlad Seryakov wrote:
Can i do this from other thread, spawn in one and check in another,
actually this is what i need. I can have multiple processes running,
then according to some rules i will check which one is taking too long
and kill it.
Currently no as you can't
Can i do this from other thread, spawn in one and check in another,
actually this is what i need. I can have multiple processes running,
then according to some rules i will check which one is taking too long
and kill it.
Zoran Vasiljevic wrote:
On 14.09.2006, at 19:50, Vlad Seryakov wrote:
T
On 14.09.2006, at 19:50, Vlad Seryakov wrote:
The only immediate request i would have for ns_proxy to be able to
query
pid for active proxies, may be ns_proxy active could return pid or
other
command, that will be useful for forcing process exit if necessary.
You can do:
ns_proxy clear
The only immediate request i would have for ns_proxy to be able to query
pid for active proxies, may be ns_proxy active could return pid or other
command, that will be useful for forcing process exit if necessary.
Zoran Vasiljevic wrote:
Hi!
Motivated by the Vlad's recent report, I took anoth
Hi!
Motivated by the Vlad's recent report, I took another
tour arround the code and did yet-another cleanup phase.
Amazing howmany things you can find when you revisit the
code after some time...
I have fixed numerous MT-safeness problems, removed the
"-minslaves" config option and added new [ns
29 matches
Mail list logo
