[osiris-devel] Osiris 2.4.* - 'config' command loops in (approx) 40% cases

[Alexei_Roudnev]

'config' loops, approx. in 20 - 40% cases, when I ask it for the new host
(new means - 'osirismd' was not asked yet).

Verified at all 2.4.* versions.

OS - Win2K.

After I kill (^C) osiris and start it again, it always works instantly for
the same host (but can loop for another one). Even when I restarted osirisd
and osirismd, it works instantly. But, when I try it next time, it may
repeat.

Loop is somewhere between osiris (80% CPU) and osirismd (20% CPU).
Unfortunately, we have not build in DEBUG mode, so
it is slightly difficult to use debugger (with debugger, it should be 1
minute to figure out a reason).

I have such effect on both, test system (my desktop) and production system
(running 2.4.0-rc3 + few patches).

Any ideas? (If you have not, I'll try to compile it in debug mode, but it's
annoying because there are many directories, no global
workspace, and !@# MS GUI to the compiler... And I must compile SSL etc
first...).