Changi NNTP Server 1.0
[
Bottom of Page |
Previous Page |
Next Page |
Table of Contents ]
The following list presents solutions and workarounds to common
problems.
Installation
Connecting newsreaders
Connecting feeds
Other
Changi doesn't and never will work with filesystems with
limited 8.3 file names. In addition Changi would run
very badly on filesystems with sequentially accessed
directories, because some news subdirectories may easily
get filled with several thousand files.
[Top of Page]
Works like designed. You need to run
CHANGI.EXE constantly for
your newsreader clients. Running
CHANX.EXE will
update your newsbase, unless you're connected to a pushfeed.
[Top of Page]
The NNTPSERVER environment conflicts with my newsreader
If you define NNTPNEIGHBOR,
Changi will ignore NNTPSERVER.
[Top of Page]
Either your newsreader doesn't support XOVER or your
overview base needs to be updated.
Use another newsreader (NR/2 supports XOVER) or run
chanco oversync normal to let
Changi rebuild all overview files in the
background.
[Top of Page]
It is not possible to call Changi from inetd. Unlike common
UNIX implementations, TCP/IP
sockets are not part of the OS/2
kernel. Inetd uses a very special method of calling
servers, which is difficult to implement into a multithreaded
server like Changi.
[Top of Page]
After changing to CHANGIWORKDIR
and typing ifconfig lo 127.0.0.1
followed by start changi followed by nr2 127.0.0.1,
NR/2 appears, shuts down and reappears without any news.
Fortunately, Martin Knaup found a solution.
This problem may appear if you previously used NR/2 to read
news online from your provider's newsserver and later switched
back to Changi. It looks like an entry will have been left in
TCPOS2.INI under Application CONNECTION / Key CURRENT_CONNECTION,
which seems to force NR/2 to ignore the server given on the
command line.
Removing the CURRENT_CONNECTION entry in TCPOS2.INI solves
the problem. There are no side effects reported so far. You need
an Ini-File-Editor to do that.
[Top of Page]
When Chanx
first issues the NEWNEWS command the ISP server may
need some time to dispense the first article-ids. Minutes later
the next bunch of ids follows. It seems the server is heavily
loaded with this job.
Reduce the number of concurrent
Chanx threads with option -n.
Try to use an asterisk in your newsgroup list of host.last
wherever possible. Don't use newsrc as your list of groups. If
all this doesn't help, try to run Chanx with option -mw or -mx.
[Top of Page]
Let's assume your provider's news server is news.ping.de. Then
CHANGIWORKDIR\ping.de\news.last is the file you're looking for.
This file will be created when you call
Chanx for the very
first time, when case you must supply date, time and a
list of newsgroups.
[Top of Page]
Check your environment variable definitions in the config.sys again. They
should neither contain leading nor trailing spaces.
[Top of Page]
Exclude junk from your host.last or newsrc file.
Also make sure that you've included all the newsgroups you're
downloading (the ones in your .last file) in your
active file.
[Top of Page]
In that case Changi is not for you. Try Gigo,
a fidonet-usenet gate written by Jason Fessler and available at
www.gigo.com.
[
Top of Page |
Previous Page |
Next Page |
Table of Contents ]