[leafnode-list] New Work In Progress Snapshot of 2.0b8_ma series available

[Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----

Hi,

I'm just uploading leafnode-pcre-2.0b8_ma-pre3-WIP-20010509-1.tar.bz2 to
the usual location, http://mandree.home.pages.de/leafnode/beta/

As usual, no warranties, may eat your data, may turn your brain into a
sponge. Use at your own risk. Report problems, please.

========================================================================
*** INCOMPATIBLE CHANGE ***
IMPORTANT: you must rename all files in leaf.node that don't have a
colon and a port number so that they now have a trailing :0,
i. e. (EXAMPLE):

cd /var/spool/news/leaf.node/
mv news.cis.dfn.de news.cis.dfn.de:0

Do that for all files except groupinfo. groupinfo keeps its name.
========================================================================

NOTE: fetchnews will fetch newsgroups lists all over again on the
*first* run of WIP 20010509, it records that event in leaf.node/ in a
file named last:SERVER.NAME:PORT.

========================================================================

Important changes in addition to those shown above:

- - per-server tracking of the last time the active has been read from a
  server. Less code, different approach, more reliable.

- - drop XGTITLE support. It is no longer part of the current nntpext IETF
  draft.

- - fix LISTGROUP command. Its handler forgot to pass the newsgroup back
  to nntpd, which broke tin 1.4.4 (NOT a tin bug, tin falls victim to
  nntpd bugs here; tin showed the contents of the wrong news group). I
  broke that recently.

- - the lockfile always carries the PID now, could fail formerly if
  interrupted early; lock files without PID were never considered stale
  (security reasons). NOTE: all leafnode daemons and programs must run
  on the same machine. While the locking is NFS safe, this is only so
  that it doesn't fail on Network Attached Storage. If you'd run
  fetchnews on one machine and on the same news spool a texpire on
  another machine, texpire will happily collect the lock file. I think
  this is not going to be fixed since I'm going to dispose of the
  locking and implement a different groupinfo access scheme soon.

- -- 
Matthias Andree

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
Comment: Processed by Mailcrypt 3.5.5, an Emacs/PGP interface

iQCVAwUBOviWiydEoB0mv1ypAQGTWwQAsCAULEXmrfmtK4Qe2BpA4rl1As9sLKLt
o6sqh0lGUZBtLO5+bZs6z54/MJ59pSRWP9l9MzrPvZm79GcjkxYTHVbJrV4B+BoO
7O5Nz1B4RG2EedfXMpRKQc/NLbBD0ezenJsceo3U8SQmibLqko27zlFifBhtGqI+
oAbyDXOlySQ=
=OJvN
-----END PGP SIGNATURE-----

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list