Changi NNTP Server 1.2

[ Bottom of Page | Previous Page | Next Page | Table of Contents | Index ]

Known Bugs

This chapter is under construction.

Changi is under permanent development. Many people around the world have been and still are very helpful in detecting and reporting bugs. Most of these bugs had been removed, but some remaining problems had been discovered too late, while others will require some major code changes.

Under no circumstances Changi should be considered free of bugs. It had been very well tested and will satisfy its users in most environments. But because of its flexibility and the resulting complexity, it is impossible to verify each possible combinations of varying installations.

If you think you discovered an unknown program bug, see the chapter about "Reporting Bugs how you can help to improve this product.

'cunbatch' or 'gunbatch'

'gunbatch' is the common keyword when using gzip for compression. But not every uplink might support it.

Unfortunately there isn't any specific environment setting to change this behaviour, but we are lucky that Changi is buggy at that point.

The server uses the lowercase of the first character of CHANGICOMPRESSCALL, which defaults to gzip -c. Putting gzip on drive c: and setting CHANGICOMPRESSCALL to c:\gzip -c should do the trick.


Articles in Removed Groups Never Expire After Rebuild

If you removed any newsgroup, either by editing the active file or calling chanco rmgroup, the remaining articles are not removed. They will expire in the normal way and vanish after their expire period.

However, when rebuilding the history index, then all message-ids of articles within removed newsgroups will be lost. As a result these articles will never expire and remain on your disk until deleted manually.

Articles not Expired in Virtual Groups

Articles in virtual groups like local.reference won't get expired unless rebuilding the history.

Articles are Removed Only After All Crossposts Expired

Expire is not able to remove articles, unless all it's crossposts are expired too. If you setup different expiration dates on different groups, some articles may live long in groups with short expiration times, if they are crossposted to groups with long term expiration.


Changi And Expire in an Endless Loop

If Changi hasn't been terminated properly, the history index might have got corrupted. The recommended way is to run Expire with option -V prior to restarting the server. In case of reported errors you should run Expire with option -r to rebuild the index.

Under rare circumstances Expire will fail while checking the index with option -V, and keeps running in an endless loop.

In critical applications you may generally run Expire with option -r before starting the server. But be aware, that this will destroy remembered message-ids and increase the danger of accepting late duplicates. Before running Expire you may additionally check for the existence of CHANGI.PID. Finding this file in CHANGIWORKDIR after rebooting is an indication that the server didn't shutdown properly.


Changi And UUPC Not Working Under 4OS2

Rnews is running badly when called by uuxqt under the 4OS2 shell.

Call uuxqt with CMD.EXE shell.


Changi Fails if Waiting for sendmail

If Changi calls sendmail while processing a local post to a moderated group, it may fail if sendmail hangs because of DNS timeout or other problems.

Make sure that sendmail is working before trying to post to a moderated group.


[ Top of Page | Previous Page | Next Page | Table of Contents ]


URL: changi/manual/betatest.html
Created: 29 December 1996
Revised: 9 January 1997
Author: harald@os2point.ping.de