rsync.nlm ABEND, time by time.

Hi.

>
>You may as well throw SP8 at this server,

Novell Open Enterprise Server, NetWare 6.5
Support Pack Revision 08

>but if it still abends you'll
>just have to try to diagnose what action or event triggers Rsync to
>abend and avoid it -

That's what I would love to do. All I can see so far is that it happens just
*SOMETIMES* when data come in from the "rsync pushing PC".

How to further distinguish what exactly is the issue?
(rsync data - e.g. wrong encoding, rsync commands, ... ?)

I was already thinking of wire tap that server and to whireshark all the traffic to
it, but I doubt, that I could see what is triggering the ABEND...

>rsync being unsupported and all.

But "unload kill address space = <some-address-space>" *IS* supported? ;)

I expected, that this command works about this like:

"Hi User Space Process! Thanks for your PID, for the RAM, and RIP! <shot>"

Doesn't look like killing an address space is that straight and simple? What's going
on back stage when killing address spaces?



Another question: Is there a way to specify for abend handling, that *IF* the
offending process is running protected, that it should be directly suspended
whithout jumping to the abend info page -- and this *ONLY* if the offending process
is running protected!




Regards, Rudi.