It appears that there may be a bug in the handling of peered lists that
have "Files=Yes" specified.  We have had a locally peered list loop on
us twice when a file was punched to the list - this was a "known working"
application that distributed our user services newsletter every week for
the last several months - it broke when 1.7F came out.  However, being a
weekly thing, we didn't isolate it immediately, and figured it for a fluke.
 
Tonight, the SAS-L list did the same thing, spawning off at least 150 copies
of file.  I've forwarded copies of the problem file at various stages of
the loop to Eric.
 
                                  Valdis Kletnieks
                                  Computer Systems Engineer
                                  Virginia Polytechnic Institute