🚀 go-pugleaf

In article <1isho3INN1mb@rodan.UU.NET> rsalz@rodan.UU.NET (Rich Salz) writes:
> 
> In <KATZ.93Jan11110023@carbon.elements.rpal.rockwell.com> katz@rpal.rockwell.com writes:
>>Can some tell me what causes error messages of the form shown below in
>>INN?
>>Jan 11 09:57:47 carbon innd: ME cant update_active talk.politics.misc
>>Jan 11 09:58:15 carbon innd: ME cant update_active soc.motss
> It tried to assign an article number that is too big to fit into your
> active file.
> 
>>I then nfs mounted the new location on the old ...
> Most people believe that it is best to have the spool directory be a local
> filesystem on the same host where innd or relaynews resides.  They believe
> this to be even more true of the lib directory.  Nobody can directly point
> fingers at NFS bugs or (mis-)features that cause problems, but experienced
> sys admins are generally very paranoid about doing this.  Just a data point.
> 
The file system is nfs mounted to another partition on the same
machine.  Is there a better way of donig things if one is forced to
move news to a different partition due to a shortage of disk space in
its current partition.  That is, is there a solution short of
reinstalling inn and specifying a new location for articles at
installation time.

>>I know that this can happen as a result of doing something like tar to
>>copy news and thereby splitting cross-posted articles.
> No, INN will revert to symlinks fine.  Make sure to use the -l flag in
> your expire, however.  See also the caveats in news-recovery.8.
> 	/r$

I am a little confused.  Under what circumstances does inn instroduce
sym links?  Before I moved my news spool and nfs mounted it I never
used the -l flag and never had any problems.  Does the nfs mounting
cause inn to create sym links?
--
------------------------------------------------------
Morry Katz
Rockwell Science Center
administrator@rpal.rockwell.com (machine administration issues)
katz@rpal.rockwell.com (other)
------------------------------------------------------