> Some of our customer do. Yet, module-wise they use only NS common
> modules (nslog, nssock, nsperm...) plus number of our proprietary
> modules on SuSE 64bit Linux box.
Our provider set up a new system with 64bit unaskedly, I ordered 32bit.
I don't want to run into any open or hidden traps - no
Am 28.06.2006 um 07:33 schrieb Bernd Eidenschink:
Does one of you use Naviserver with common modules on a 64bit
architecture?
On a production system?
Some of our customer do. Yet, module-wise they use only NS common
modules (nslog, nssock, nsperm...) plus number of our proprietary
modules o
Hi!
Does one of you use Naviserver with common modules on a 64bit architecture?
On a production system?
Thanks,
Bernd.
On 6/27/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Am 27.06.2006 um 18:15 schrieb Stephen Deasey:
>
> There's no default timeout in the current code, and the error
> message should be:
>
> timeout waiting for concurent update: ...
>
> Make sure you're testing code from HEAD.
Easier sa
Am 27.06.2006 um 18:15 schrieb Stephen Deasey:
There's no default timeout in the current code, and the error
message should be:
timeout waiting for concurent update: ...
Make sure you're testing code from HEAD.
Easier said than done. The HEAD is not usable for testing
as the code we
On 6/27/06, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Am 27.06.2006 um 13:33 schrieb Zoran Vasiljevic:
> Hi !
>
> I got the same report from customers:
>
>timeout waiting for update: 59331.0.n.childs
>
> We never use anything except ns_cache_create, ns_cache_flush
> and ns_cache_eval comm
Am 27.06.2006 um 13:33 schrieb Zoran Vasiljevic:
Hi !
I got the same report from customers:
timeout waiting for update: 59331.0.n.childs
We never use anything except ns_cache_create, ns_cache_flush
and ns_cache_eval commands.
This might be if the default value of cacheTimeout of 3 secon
Hi !
I got the same report from customers:
timeout waiting for update: 59331.0.n.childs
We never use anything except ns_cache_create, ns_cache_flush
and ns_cache_eval commands.
This kind of error was happening much more often before and
I have tried to fix that bug some days ago. Aparently I
