<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.network.leafnode">
    <title>gmane.network.leafnode</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4667"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4666"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4665"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4664"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4663"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4662"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4661"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4660"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4659"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4658"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4657"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4656"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4655"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4654"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4653"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4652"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4651"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4650"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4649"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.leafnode/4648"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4667">
    <title>Re: checkgroups usage</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4667</link>
    <description>&lt;pre&gt;

Hmm, is ok to remove servers listed at:

/var/spool/news/leaf.node


or is there a way to do that through a leafnode command?  I don't want 
leafnode to use some of the servers listed.



thanks,

Thufir

&lt;/pre&gt;</description>
    <dc:creator>Thufir</dc:creator>
    <dc:date>2013-05-20T01:03:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4666">
    <title>Re: checkgroups usage</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4666</link>
    <description>&lt;pre&gt;

oh, fetchnews -f to get new groups looks better.  dunno why I didn't see 
that earlier.

&lt;/pre&gt;</description>
    <dc:creator>Thufir</dc:creator>
    <dc:date>2013-05-19T22:43:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4665">
    <title>checkgroups usage</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4665</link>
    <description>&lt;pre&gt;I've removed the gmane group from the config, but gmane keeps showing up 
in interesting groups.  I think this can be fixed with checkgroups?

Am I not doing this correctly?


root&amp;lt; at &amp;gt;dur:~# 
root&amp;lt; at &amp;gt;dur:~# head -n 3 /var/spool/news/leaf.node/groupinfo 
0 1 2 1368645998 0 0 
0.akita-inu 1 2 1368645998 0.akita-inu
0.alaskan-malamute 1 2 1368645998 0.alaskan-malamute
root&amp;lt; at &amp;gt;dur:~# 
root&amp;lt; at &amp;gt;dur:~# checkgroups /var/spool/news/leaf.node/groupinfo 
cannot read configuration.
root&amp;lt; at &amp;gt;dur:~# 



thanks,

Thufir

&lt;/pre&gt;</description>
    <dc:creator>Thufir</dc:creator>
    <dc:date>2013-05-19T21:18:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4664">
    <title>Re: Running trn with Leafnode?</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4664</link>
    <description>&lt;pre&gt;


Going off on a tangent a bit, but see

http://serverfault.com/questions/363095/

for the difference between 127.0.1.1 and 127.0.0.1 with regards to debian 
type systems.


-Thufir

&lt;/pre&gt;</description>
    <dc:creator>Thufir Hawat</dc:creator>
    <dc:date>2013-04-07T08:43:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4663">
    <title>Re: Running trn with Leafnode?</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4663</link>
    <description>&lt;pre&gt;



If it helps, here are my settings to accomplish that:

thufir&amp;lt; at &amp;gt;dur:~$ 
thufir&amp;lt; at &amp;gt;dur:~$ cat /etc/hosts
127.0.0.1localhost
127.0.1.1dur.bounceme.netdur

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
thufir&amp;lt; at &amp;gt;dur:~$ 
thufir&amp;lt; at &amp;gt;dur:~$ cat /etc/hostname 
dur
thufir&amp;lt; at &amp;gt;dur:~$ 

although I wonder that maybe that hostname file shouldn't be set to 
dur.bounceme.net?  Anyhow, seems to work, I guess because dur is in /etc/
hosts.  Hmm, actually, looking at the IP addresses for localhost versus 
dur in /etc/hosts makes me wonder if that's correct...

just be sure to acquire a FQDN from no-ip.com or a similar provider.


HTH,

Thufir

&lt;/pre&gt;</description>
    <dc:creator>Thufir Hawat</dc:creator>
    <dc:date>2013-04-07T08:39:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4662">
    <title>Re: Running trn with Leafnode?</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4662</link>
    <description>&lt;pre&gt;
The short explanation is:
1) Run leafnode as server
2) connect your newsreader to localhost

I would do the following:

`telnet localhost 119` to see if there is a newsserver running on your
machine. (Be sure that it can not be contacted from anywhere else.) IF
that works, great. When logged in with TELNET type `LIST` which will show
you groups. If you see many groups, then you have already retrieved
things. If not, then you did not.
Do a `fetchnews -vvv` and see what happens.

If there are no errors there, then it might be a trn issue. Post a test
message (to a test group)
http://www.anta.net/misc/telnet-troubleshooting/nntp.shtml
After posting, run `fetchnews -vvv` again.

Also look at the 'interested.groups' directory and add do as root `touch
alt.test` to be sure at least that group is available.
Run `fetchnews -vvv` again if you have added it.

If telnet to port 119 on localhost is not working, you are not yet have a
running leafnode. Read all the files that come with it and explain here in
detail what&lt;/pre&gt;</description>
    <dc:creator>houghi</dc:creator>
    <dc:date>2013-04-07T08:09:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4661">
    <title>Re: Running trn with Leafnode?</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4661</link>
    <description>&lt;pre&gt;
RIght, it's not a function of either trn or leafnode. Trn will work with any
NNTP server, including Leafnode. On my OS, Gentoo, I believe leafnode has a
dependency on xinetd, which is configured as following:

/etc/xinetd.d/leafnode

service nntp
{
        disable         = no
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = news
        flags           = REUSE
        server          = /usr/sbin/leafnode
        bind            = 127.0.0.1
        log_on_failure  += USERID
}

xinetd is simply started at boot, at leafnode automatically binds to
127.0.0.1 (localhost). Of course your hosts file will have to be sane for it
to work.

I'm sure there are many ways of binding leafnode to localhost, and directing
trn to 127.0.0.1. :)
&lt;/pre&gt;</description>
    <dc:creator>ny6p01-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-04-07T01:46:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4660">
    <title>Re: Running trn with Leafnode?</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4660</link>
    <description>&lt;pre&gt;

I can say that with Pan, I just add leafnode as a NNTP server.  In my 
case, it's just "localhost" for the name of the nntp server.

You have your hostname and FQDN sorted out as per leafnode manual?


HTH,

Thufir

&lt;/pre&gt;</description>
    <dc:creator>Thufir Hawat</dc:creator>
    <dc:date>2013-04-06T19:54:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4659">
    <title>Running trn with Leafnode?</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4659</link>
    <description>&lt;pre&gt;Well, in asking this in blind Linux lists-and-elsewhere, I installed Leafnode 
here in Debian, but my binary news-reader of choice is trn.  Cannn some1 please 
inform on steps I can have these 2 work together?  From what I understand 
Leafnode can open a portion of a group, which would be great as trn crashes on 
larger groups-and-increasing article numbers.
As of now I am running trn with an rn script, like this:
#!/bin/sh
# run trn
/usr/bin/trn -J5 -G -x0sml "-X1XD" -Ots -e -M +m -t -h +hfrom +Hnewsgr "$&amp;lt; at &amp;gt;"
# move any clarinet.* groups to .newsrc.clari
#mv-clari
# re-sort the .newsrc file
sortrc
Back again live, I already edited a config with giganews  related items, but 
have no idea if any changes need to go in my .newsrc or .trnrc, ETC.
Thanks so very much in advance
Hart
&lt;/pre&gt;</description>
    <dc:creator>Hart Larry</dc:creator>
    <dc:date>2013-04-06T01:14:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4658">
    <title>Leafnode-List administrivia "Mail forwarding loop"</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4658</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

Some of you may recently have received "Undelivered Mail returned to
send" with a "Mail forwarding loop" complaint from
MAILER-DAEMON-DcxqERLcJkSjd9KveT9UGqzufkE7zoXZyCaAmVia5Yk&amp;lt; at &amp;gt;public.gmane.org recently.

If you did not, skip this message.

If you did: THIS IS NOT YOUR FAULT, and you NEED NOT RESEND your
messages -- your list posts have been processed properly.  The only
thing is that one of the subscribers had - through misconfiguration or
by accident or other misfortune - caused /your/ messages to be re-sent
to the list, and this caused half a dozen complaints for me.

I have set the "nomail" flag for the offending list subscriber address,
and sent him a separate heads-up message in what I believe to be his/her
native language, explaining the problem and asking him/her to resolve it.

Again, except for the list subscriber who was notified off-list,
YOU NEED NOT take any action.  Your subscription to the list, and the
processing of your messages se&lt;/pre&gt;</description>
    <dc:creator>Matthias Andree</dc:creator>
    <dc:date>2012-11-24T10:23:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4657">
    <title>Re: illegal headers</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4657</link>
    <description>&lt;pre&gt;On Wed, 7 Nov 2012 06:28:17 +0000 (UTC) thufir &amp;lt;hawat.thufir-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
wrote:


What does that file look like?  Does it exist?  Is it mentioned
in /var/log/news.log (or whatever your news log file is)?  What does the
entry for that article number
in /var/spool/news/comp/os/linux/advocacy/.overview look like?

&lt;/pre&gt;</description>
    <dc:creator>Whiskers</dc:creator>
    <dc:date>2012-11-07T19:04:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4656">
    <title>illegal headers</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4656</link>
    <description>&lt;pre&gt;when leafnode finds illegal headers:


root&amp;lt; at &amp;gt;dur:~# article /var/spool/news/comp/os/linux/advocacy/6401 contained 
illegal headers: non-printable characters in headers (relaxed check 
allows for iso-8859*)



does it remove that article from the spool?



thanks,

Thufir

&lt;/pre&gt;</description>
    <dc:creator>thufir</dc:creator>
    <dc:date>2012-11-07T06:28:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4655">
    <title>Re: HEADS UP Clemens Fischer, lua authentication bugs, and your mail is non-functional</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4655</link>
    <description>&lt;pre&gt;Am 01.11.2012 14:54, schrieb Matthias Andree:


Done - it's dubbed 20121101a. Sorry for the duplicate announcement -
script bugs (now fixed).

&lt;/pre&gt;</description>
    <dc:creator>Matthias Andree</dc:creator>
    <dc:date>2012-11-01T14:40:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4654">
    <title>leafnode-2.0.0.alpha20121101a snapshot available</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4654</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Leafnode 2.0.0.alpha20121101a is available from
http://home.pages.de/~mandree/leafnode/beta/

NEWS:
KNOWN BUGS:
* The code sometimes uses timeout_client where it should use a server timeout.
|
2.0.0.alpha20121101a: Changes since 20110807a:
+ Bugfix: if reading descriptions of new newsgroups fails, don't update
  "active last updated" time stamp for that server. To solve a problem
  reported by Antoine Levitt.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAlCShf4ACgkQvmGDOQUufZXcawCgrDPyhzAgh9xHni0GEhW6YQv0
09wAniM/9vjpklgotUqMqYUC0+WzLIv5
=8wRj
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Matthias Andree</dc:creator>
    <dc:date>2012-11-01T14:23:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4653">
    <title>leafnode-2.0.0.alpha20121101a snapshot available</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4653</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Leafnode 2.0.0.alpha20121101a is available from
http://home.pages.de/~mandree/leafnode/beta/

NEWS:
KNOWN BUGS:
* The code sometimes uses timeout_client where it should use a server timeout.
|
2.0.0.alpha20121101a: Changes since 20110807a:
+ Bugfix: if reading descriptions of new newsgroups fails, don't update
  "active last updated" time stamp for that server. To solve a problem
  reported by Antoine Levitt.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlCShMQACgkQvmGDOQUufZUBgwCdF/e3X5lB9LdDuLv2jBxq8AM6
AGYAn2vBo4INt0aHZjpFfTPWUfyYHWh9
=omz5
-----END PGP SIGNATURE-----
&lt;/pre&gt;</description>
    <dc:creator>Matthias Andree</dc:creator>
    <dc:date>2012-11-01T14:18:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4652">
    <title>HEADS UP Clemens Fischer, lua authentication bugs, and your mail is non-functional</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4652</link>
    <description>&lt;pre&gt;Clemens,

sorry to contact you this way, and I hope you are seeing this through
GMANE - your dnsalias.org address is dysfunctional, so my mail bounced.

In de.comm.software.newsserver are complains - and I could verify them -
that authentication is broken in the lua version of leafnode.  I suppose
that this is an artifact of an incomplete groupauth implementation.

The detailed complaint is that the luascript version of leafnode will
behave as though no authentication is required, i. e. lets users see all
groups, post everywhere, without authentication.


Can you please see to that:

- with --disable-lua, traditional leafnode behaviour is reinstated, i.
e. global authentication required for mostly everything that affects
groups or articles

- in the absense of Lua scripts, traditional leafnode behaviour is
reinstated, same conditions as above


I have, in the meanwhile, fixed some paths for the scripting, but I seem
to be unable to get groupauthentication running. There is a want_*
variable in scripthooks.lu&lt;/pre&gt;</description>
    <dc:creator>Matthias Andree</dc:creator>
    <dc:date>2012-11-01T13:54:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4651">
    <title>Re: backup or migration strategy</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4651</link>
    <description>&lt;pre&gt;
Depends on the volumes involved, of course.
But, presumeably the new HD will be *much* bigger, and the existing one has a 
few miles on it?

Why not install everything on the new disk and use the old one as a drive to 
store cron'd backups?


&lt;/pre&gt;</description>
    <dc:creator>Werner Geuens</dc:creator>
    <dc:date>2012-09-30T18:19:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4650">
    <title>Re: backup or migration strategy</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4650</link>
    <description>&lt;pre&gt;



I'm doing a clean install onto a larger hard drive:

https://help.ubuntu.com/community/Installation/FromLinux#Without_CD

and will now have this extra disc, so I was thinking it might make sense 
to utilize it just for news?


-Thufir

&lt;/pre&gt;</description>
    <dc:creator>Thufir</dc:creator>
    <dc:date>2012-09-29T19:35:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4649">
    <title>Re: re-fetch</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4649</link>
    <description>&lt;pre&gt;

No worries.  I just like leafnode alot :)


-Thufir

&lt;/pre&gt;</description>
    <dc:creator>Thufir</dc:creator>
    <dc:date>2012-09-20T03:18:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4648">
    <title>Re: re-fetch</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4648</link>
    <description>&lt;pre&gt;Am 10.09.2012 08:36, schrieb Thufir:

No there is not. Given that it is only an environment variable, it was a
quick hack, rather than a first-class feature...

Sorry.


&lt;/pre&gt;</description>
    <dc:creator>Matthias Andree</dc:creator>
    <dc:date>2012-09-19T18:45:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.leafnode/4647">
    <title>Re: backup or migration strategy</title>
    <link>http://permalink.gmane.org/gmane.network.leafnode/4647</link>
    <description>&lt;pre&gt;Am 17.09.2012 23:18, schrieb Thufir:

Yes, you can.

It is, however, important that tar, pax, cpio, or whichever tool you
use, is (A) capable of, and (B) instructed to save and restore
hard links as hard links (rather than just copies). Each article has
only one file (inode, technically speaking) with multiple names (= hard
links). This makes sure that we do not waste space (inodes and blocks)
on the file systems while maintaining fast access both by article number
and by message ID.

If the tool was incapable and/or improperly configured, texpire -r is
required - after unpacking the archive - to restore the hard links (and
can take quite a while to run in this case).

Also, with leafnode-1 versions, texpire -r is advised after untarring
the spool if and only if the configured name of the spooldir has changed
(because it was, unfortunately, part of the hash for access by message.ids).

It is also generally advisable to use a file system that uses hashes or
trees to manage its files per directory.


While pos&lt;/pre&gt;</description>
    <dc:creator>Matthias Andree</dc:creator>
    <dc:date>2012-09-18T18:38:17</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.leafnode">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.leafnode</link>
  </textinput>
</rdf:RDF>
