> well... I'd like to know how to fix that issue :( I'm at loss

OK, took the "hard" way, but solved it; reinstalled ActivePerl
on a different machine and then proceeded installing all the
ASSP required additional modules; zipped the c:\perl folder
and moved the zip to the ASSP machine, stopped ASSP,
renamed the current "c:\perl" folder and recreated it by
extracting files from the zip; then I started ASSP and all
was ok... aside one small glitch :)

Due to the "missing" zlib the "global PB" wasn't working, so,
as soon as I started ASSP, it uploaded the local PB-black,
then downloaded the remote one and started the "merge"
process, at that point ASSP was "blind and deaf"; I mean,
while merging the PDB, ASSP didn't answer on 25/tcp and
Perl took around 50% CPU and allocated a bunch of RAM;
after that, things went back to normal

Not really an issue, but something to keep in mind when you
see ASSP "eating CPU" and being (apparently) "stuck"; maybe
Fritz could shed some more light, but I suspect that while the
"merge" takes place, ASSP does "nothing else"

anyways, after the merge completed and CPU/RAM went back
down to normal, I stopped ASSP and updated to the latest ".26"
and till now, everything seems to be working fine



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to