
BUG REPORTING
=-=-=-=-=-=-=
If you wish to report a bug, please keep the following things in
mind:

	o	due to the low cost of this product, I can't provide "full"
		support.  Therefore, if at all possible, try to track down
		the cause of the bug.

	o	If you can suggest a workaround for the bug, that would be
		excellent.  Then, I can update the master source and issue
		a new revision.

	o	If you are unable to track down the source of the bug, please
		provide as much information as possible (ie:  did you modify
		the source, or is it stock?  Under what conditions does the
		bug occur, ("sin ver" and "sin" are usefull)?  If you didn't
		modify the source, can you send a dump file? etc).

To track bugs, I generally compile everything with -g2 and then use
the Beta 10.6 WD debugger to step through and see what died with the
dump file.  Therefore, running "dumper" is also a good idea.

Bug reports can be sent to "rk@parse.com".

KNOWN BUGS
-=-=-=-=-=
The following are known bugs:

	1	if knews is aborted during writing of the active file, the
		active file will be corrupted.

	2	control messages are filed along with the regular news, instead
		of being interpreted.

	3	reloading of the journal files is slow

	4	no history is maintained, therefore, it is possible to receive
		duplicate articles.

