Do not forget  the one major drawback: with  the 'obvious' configuration,
if  ONE list  runs out  of archive  space because  of a  mailing loop  or
whatever, ALL lists are suddenly out  of archive space and (if you didn't
follow the guidelines in the 1.7b release notes) LISTSERV's A-disk is out
of space and everything suddenly dies. SFS still has a way to go in terms
of servicing  critical applications,  unfortunately; minidisks  are still
your best bet for things you want to provide guaranteed space to.
 
Now that I think  about it... If the SFS server dies or  runs out of disk
space or whatever,  and LISTSERV is running off a  191 minidisk, does SFS
abend LISTSERV? If so, SFS has an  even longer way to go than I initially
thought - there are, after all,  return codes to disk I/O operations that
can be used to say "sorry, can't do".
 
  Eric