DIABLO is a backbone news transit system, designed to replace INND on backbone machines. The transit part of diablo is well established and should work flawlessly. You cannot run the transit server portion of diablo on a machine which needs to accept nntp post commands or newsreading-related nntp commands. You cannot point your NNTPSERVER at a host running the transit portion of Diablo.
Diablo is an extremely efficient news transport and reading system. I have been running Diablo on BEST Internet's backbone news machine for over a year without problems. In fact, since I left BEST in January 1999 I think the system has been running almost entirely on autopilot! :-)
If you have a dedicated newsfeeds machine which does feeds, feeds, and nothing but feeds, Diablo may be for you.
Y2K ISSUES - We have audited Diablo and do not believe there to be any Y2K issues. This can't be guarenteed, of course, but if any problems do crop up they will almost certainly be so minor that a fix will be available within a day or two of the event.
As of 1.14, Diablo now uses a CRC-63. Users upgrading from older Diablo releases should probably just do a clean wipe. It is possible to upgrade without wiping the history file out, but it isn't trivial. The benchmark program and test results on an 18.2 million message-id dataset can be found by Clicking Here
Diablo was written and is currently being maintained by Matthew Dillon, http://www.backplane.com/, you can mail me at: dillon at backplane.com
You need XMake to compile up Diablo, please refer to http://www.backplane.com/xmake/
For recommended hardware configurations, please see Hardware Configuration Recommendations
A serious bug with the auth code has been fixed by Russell.
Lots of new features added by Russell Vincent.
Added mid-level cache handling features to make midlevel reader caches actually useful.
More bug fixes from Nickolai
A huge patchset by Nickolai Zeldovich
A minor Y2K bug relating to the parsing of 2-digit years in the
Date: field has been fixed. Minor because most usenet postings
use 4-digit years.
A minor Y2K bug relating to the parsing of 2-digit years in the Date: field has been fixed. Minor because most usenet postings use 4-digit years.
Fixed a bunch of bugs with patchset submitted by
This is a maintenance release which fixes a few minor bugs and documents reader<->server operations a little more.
Relative to 1.22, this release fixes a bug that came up with FreeBSD-3.1 and 4.x, which may also be true of other platforms. When reading a local socketpair() stream type tcp socket with non-blocking set, the read may return fewer bytes then were written on the other side.
Relative to 1.20, this release also fixes a huge number of bugs.
Manual pages are available:
Contributor's web pages are listed below (this is a new section, so it is somewhat incomplete right now):
Here is a listing of the tar (for 1.20-REL):
[an error occurred while processing this directive]