> ...     The complaints come from sites which
> have a good number  of large local lists, sometimes with  as much as 1000
> subscribers on them,  and who've got to justify every  second of CPU time
> spent on network (ie non-local) services.  I don't really know what to do
> there. They could be allowed to  disable netwide functions, but then what
> happens if they do have a few  non-local lists (that is usually the case,
> even if most lists  are local)? What if a local user  does a SIGNOFF with
> the NETWIDE  option and doesn't  get signed  off these lists  because the
> function is disabled?
 
Could it be set up so that NETWIDE ignores local lists, at least as a
site option?  Would this solve the problem?
 
/Leonard