At 01:29 AM 1/5/01 -0800, you wrote:
>Hi,
>
>I've found the following problem.
>
>---- dnews.conf ----
>diskspace 30000
>spool /u2
>diskspace2 30000
>spool2 /u3
>diskspace3 30000
>spool3 /u4
>diskspace4 30000
>spool4 /u5
>workarea /u1/work
>workarea_min 5
>history /u1/history
>history_min 5
>history_moved true
>xover_dir /u1/xover
>xover_cache 15000
>xover_moved true
>---------------------
>/u1, /u2, /u3, /u4 and /u5 is a separate 36GB disks. With the above config
>dnews is using only the first storage (spool) and nothing is going to
>spool2, spool3, spool4. When the /u2 is 100% full, "tellnews status" shows
>"Used: XXXMB=27%" and on the next line "** Spool area full". All feeds are
>closed.
>I've changed "history_moved true" to "false" and "xover_moved true" to
>"false" and now all spool areas are in use by dnews.
>
>Is it a bug, or I've missed something?
Do you have
spool_free true
set in dnews.conf? if so change it to false
You can safely manually move some bucket files from the full partition to
another one then restart dnews to unjam it
If that doesn't fix it, please send me:
dnews.conf
tellnews status
tellnews showdisks
ChrisP.
