At 04:44 AM 12/31/00 -0800, you wrote:
>After installing and configuring dnews on an NT4 server to provide just
>local groups but for Internet users (providing discussion forums) I'm
>having a perplexing time.
>
>I have the following folder layout:
>
>gf\news
>gf\news\web
>gf\news\work
>gf\news\spool
>etc...
>
>dnews was installed to the gf\dnews folder. All the executables, config
>files, and so on are in that folder.
>
>My dnews.conf sets the paths to the config files:
>
>config d:\inetpub\wwwroot\h\gf\news
>
>I had
>gf\news\active.dat (default from install)
>gf\news\work\active.dat (contains all the groups I've added using dadmin)
>
>When I stopped and restarted dnews (a Server reboot actually) dnews had
>'lost' all the groups I'd entered previously and was back to the 1 group
>listed in gf\news\active.dat
>
>I copied gf\news\work\active.dat to gf\news\active.dat and restarted dnews
>and my groups re-appeared.
>
>I've been doing some further group additions using dadmin and have
>realized that I appear to be heading for the same problem:
>The working set of groups presented to nntp clients comes from the 'wrong'
>active.dat file.
>
>Am I missing something obvious here?
>
>There doesn't appear to be anywhere to specify the location of the
>active.dat file in the other config files.
>
>dnews.conf
>
>cachedall true
>manager [EMAIL PROTECTED]
>config d:\inetpub\wwwroot\h\gf\news
>logdir d:\inetpub\wwwroot\h\gf\news
>workarea d:\inetpub\wwwroot\h\gf\news\work
>history d:\inetpub\wwwroot\h\gf\news\hist
>xover_dir d:\inetpub\wwwroot\h\gf\news\xover
>spool d:\inetpub\wwwroot\h\gf\news\spool
>diskspace 500
>bind_in w.x.y.z
>bind_out w.x.y.z
>etc...
Very strange, it is definitly in the 'workarea' directory, so I suspect you
are editing the wrong dnews.conf file, or have not restarted dnews since
changing dnews.conf or something weird like that.
The dnews.conf file is in \winnt\system32\dnews.conf so triple check that
that is the file you are changing, and that you don't have multiple entries
in it for 'workarea' And maybe reboot to ensure you have restarted dnews.
ChrisP.