On 14.09.2006, at 23:02, Stephen Deasey wrote:
AtShutdown callbacks are called twice: the first time is to allow you
to notify threads that they should begin cleaning up for shutdown; the
second time you should actually wait for the shutdown to complete,
taking note of the absolute timeout va
On 9/14/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
On 14.09.2006, at 21:59, Stephen Deasey wrote:
> Currently you're cleaning up with a AtExit handler and manually
> calculating a timeout to wait for proxies to exit. I think you
> really want an AtShutdown callback. These already handle
On 14.09.2006, at 21:59, Stephen Deasey wrote:
Currently you're cleaning up with a AtExit handler and manually
calculating a timeout to wait for proxies to exit. I think you
really want an AtShutdown callback. These already handle a
notification and then timeout sequence.
I think at the mom
On 14.09.2006, at 21:59, Stephen Deasey wrote:
AtShutdown callback
Yes. That's it.
Ah. with that waiting mess I just wanted to make sure
the server will eventually exit even if I mess something
up in the reaper thread and this stucks somewhere.
On 9/13/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
On 13.09.2006, at 04:55, Vlad Seryakov wrote:
> Had ns_proxy running, typed in nscp ns_shutdown and nsd crahsed
Eh... this is true. In the attempt to cleanup as much as possible
I prematurely cleaned a pool having references to it.
Actual
No hurry, i am doing this the old-fashioned way using ns_thread for now
but ns_job-like way of handling proxies would be nice
Zoran Vasiljevic wrote:
On 13.09.2006, at 21:52, Vlad Seryakov wrote:
ok, for example i schedule encoder
ns_proxy configure channel1 -minslaves 0 -maxslaves 1
set h [
On 13.09.2006, at 21:52, Vlad Seryakov wrote:
ok, for example i schedule encoder
ns_proxy configure channel1 -minslaves 0 -maxslaves 1
set h [ns_proxy get channel1]
ns_proxy send $h "/usr/bin/mencoder "
now proxy is running and pool channel1 is taken, in another thread i
cannot just issue
ok, for example i schedule encoder
ns_proxy configure channel1 -minslaves 0 -maxslaves 1
set h [ns_proxy get channel1]
ns_proxy send $h "/usr/bin/mencoder "
now proxy is running and pool channel1 is taken, in another thread i
cannot just issue ns_proxy get channel1, it will hang.
I can ru
On 13.09.2006, at 16:45, Vlad Seryakov wrote:
Can nsproxy be extended to be able to kill any particular process
without issuing nsproxy get first, get hangs if no available
process are
in the pool. It would be nice to be able to query how many are
running
and be able to kill by pid or na
The other night i was trying to use nsproxy for long running processes,
like encoding with ability to work with them like ns_job queues,
define min. max, submit in the background, check who is running, kill if
have to.
Can nsproxy be extended to be able to kill any particular process
without i
On 13.09.2006, at 04:55, Vlad Seryakov wrote:
Had ns_proxy running, typed in nscp ns_shutdown and nsd crahsed
Eh... this is true. In the attempt to cleanup as much as possible
I prematurely cleaned a pool having references to it.
Actually, pools still having references to them should not be
t
Had ns_proxy running, typed in nscp ns_shutdown and nsd crahsed
0xe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7d5b486 in __nanosleep_nocancel () from /lib/libc.so.6
#2 0xb7d5b2ab in sleep () from /lib/libc.so.6
#3 0xb62d701c in DnsPanic (fmt=0xb7f2d34
12 matches
Mail list logo
