[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[leafnode-list] Re: database versus /var/spool/news/

To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Subject: [leafnode-list] Re: database versus /var/spool/news/
From: Matthias Andree <matthias.andree@xxxxxx>
Date: Sun, 10 Sep 2006 22:48:59 +0200
Delivery-date: Sun, 10 Sep 2006 22:50:08 +0200
List-id: Discussions on the Leafnode Usenet software package <leafnode-list.dt.e-technik.uni-dortmund.de>
Sender: leafnode-list-bounces+list01=leafnode.de@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux)

Thufir <hawat.thufir@xxxxxxxxx> writes:

> Just curious as to why messages go to /var/spool/news/ instead of into a 
> RDMS, which'd seem more natural.  This is for historical reasons?

Yes, traditional newsreaders would access /var/spool/news -- but that's
long gone. Chances are that leafnode 2.0 will still stick with that
scheme (with minor modifications) though. Accessing articles via files
is /usually/ (except for pathological cases) fast enough; .overview
(XOVER/OVER/NOV support) is a different issue though and was never part
of the original "traditional spool" format.

-- 
Matthias Andree
-- 
_______________________________________________
leafnode-list mailing list
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list
http://leafnode.sourceforge.net/

References:
- [leafnode-list] database versus /var/spool/news/
  - From: Thufir

Prev by Date: [leafnode-list] Re: Listening on ports other than 119
Next by Date: [leafnode-list] Re: Listening on ports other than 119
Previous by thread: [leafnode-list] Re: spool location
Next by thread: [leafnode-list] Listening on ports other than 119
Index(es):
- Date
- Thread