If a list-owner received a message like the following (generated when
'LISTSERV@ALBNYVM1' is asked to help "distribute" a posting from your list),
sometime between December 25 and December 28,
please note that the problem has been fixed -- explanation follows.
!----------------------------Original message----------------------------
! Command replies from RSCSV2@ALBNYVM1 are being forwarded to you.
!
! You are not allowed to use inter-server DISTRIBUTE control keywords.
! Your job (4401) has been transferred to the postmaster.
----------------------------Response from postmaster--------------------
Date:         Wed, 30 Dec 92 00:53:42 EST
From:         Ben Chi <BEC@ALBANY>
Organization: University at Albany Computing Services
 
Well, since you ask, this was quite a saga.  On Christmas day (system un-
attended), our 3084QX was feeling a little out of sorts and decided to
reboot itself, redesignating the master processor (there are 4) as pro-
cessor 2 instead of the normal processor 0.  Unfortunately, however, the
file SYSTEM NETID S contained the CPUID of only processor 0, the ultimate
result being that if a user executes IDENTIFY he gets
FOOBAR   AT ALBNYVM1 VIA *       12/25/92 12:34:56    instead of
FOOBAR   AT ALBNYVM1 VIA RSCSV2  12/25/92 12:34:56 .
This caused a LOT of things to screw up, among them LISTSERV.