One problem with the new internationalization seems to be incorrect arguments 
to the
printing functions.
Look at this end of a staging for example:

===================
6359:nsrstage: Deleting the successfully cloned save set 4137727938
Deleting save set 4137727938 clone 1184937921 from the media data base.
Successfully deleted clone 1184937921 of save set 4137727938 from media 
database
Successfully deleted AFTD's companion clone 1184937922 of save set 4137727938 
from media database
Recovering space from volume 4288722347 after successfully cloning save sets.
Ã|: read only
Ã|: space recovered from volume TempInc.01.RO
Space recovered from volume 4288722347
===================

We also had an issue with nsrmmd crashing, obviously  when trying to tell us
that something is wrong with the AFTD it was handling. The core indicated that
it crashed in strcat, which would point to a similar error as above.

The problem with these kind of crashes is that the outcome can be completely
random, depending on what happens to be in the registers....

In the second example another nono of programming also shoved up:
nsrmmd didn't handle the segmentation violation properly, but 
"forgot" to free up the shared memory used for communicating with
"save" and thus enough of these crashes started generating "cannot allocate
memory" errors after a number of nsrmmd cores. This could only be cleared
by a reboot or a ipcrm command of the orphaned shared memory segments.

Seems like the old "tradition" of not testing/handling error conditions in
Networker continues....

Best
Dag

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER