# dserver.hosts
#
# ip/host/wildcard	flags		# comment
#
# WARNING!!! dns resolution for hostnames is done synchronously and may stall
#	     readers, use IP addresses when specifying remote dns servers.
#
# flags:
#	s[#]	remote server for article fetches, w/ optional priority.
#		An article fetch is made from a random spool at the 
#		lowest priority until all spools at that priority have
#		been exhausted, then repeats the procss at the next
#		higher priority.  The fetch fails when the spool server list
#		has been exhausted.
#
#	M	indicate that a 'mode reader' should be sent to the remote 
#		server being used to fetch articles.  Allows you to use
#		a remote NNTP box to fetch articles, as long as it supports
#		fetching articles by message-id.
#
#	o[#]	remote server for POSTs, w/ optional priority.
#		POSTed articles are sent to a random server at the
#		lowest priority until that priority level is exhausted
#		through failures, then repeats the process at the next
#		higher priority.
#
#		NOTE!  The ihave protocol is used to send the article.
#		i.e. when I say POST I mean a reader client of dreaderd does
#		a POST, and dreaderd must process and forward the post via
#		the ihave protocol to some feed.
#
#	p#	specify port number on host
#	
#	R	flag to indicate that a 'mode readonly' should be sent; this
#		is mostly for use with Diablo backend spools, and to allow
#		read-only access to articles while dhistory is being rebuilt.
#
# In this example I need two localhost lines, one to access the diablo 
# feeder's spool from the reader (plus the reader runs with it's own cache 
# turned off), and the second to tell the reader that POSTings made by user 
# NNTP sessions should be transfered to the specified server.. which happens 
# to also be our locally running diablo feeder.  Note that POST's are 
# interpreted by dreaderd and the actual interaction with the feeder is 
# through the 'ihave' protocol.  Note that my diablo feeder is running on
# port 435, so I have to specify that.
#
# Finally, if the diablo feeder is not maintaining a large spool I can tell 
# the reader to try other spools.  This would allow an ISP to maintain a 
# small spool of its own (or just use dreaderd's article caching capability) 
# while farming out failured retrievals to an off-site spool, perhaps an 
# offsite news service. 
#
# Note the use of the 'M' flag.  If the spool is a DIABLO FEEDER, do *NOT* 
# use the 'M' flag.  If the spool is an INN machine and you connect to INN 
# itself, you must use the 'M' flag.  If the spool is an INN machine and you 
# connect to nnrpd, use of 'M' is optional (but more efficient if you don't).
#
# You should, however, use the 'R' flag for Diablo spools which support
# read-only mode. This will allow dreaderd to stay connected even when
# dhistory is being rebuilt. For obvious reasons, using the 'R' flag for
# outgoing spools is not useful.
#

localhost		s1Rp435
localhost		o1p435
backup1.spool.blah	s2M
backup2.spool.blah	s3M