news server
in [Slackware]
|
Prev: Dead Pool Vulture Watch
Next: Bluetooth and Slack 13
From: Aaron W. Hsu on 14 Dec 2009 22:23 barnabyh <invalid(a)address.org> writes: >I may get away just with slrn, will see, but having a local server would >probably be better as it would free me up to use different clients. What sort of filtering do you need? Aaron W. Hsu -- A professor is one who talks in someone else's sleep.
From: Aaron W. Hsu on 14 Dec 2009 22:25 barnabyh <invalid(a)address.org> writes: >Ewald Pfau wrote: >> >> When using software, which does not need a server, as slrn or tin, you may >> access the news-spool directly (in /var/spool/news) and exchange news with >> slrnpull, part of slrn. >> >> For tin, I use three lines for bash, acting as 'inews' program (configured >> as 'inews_prog' for tin): >Didn't get tin to work with this particular server, I think it's because >it does not support snews. Could you explain a little more about Snews? Some clients may not support it natively, but it may be possible to tunnel it. If it is like SSL Usenet, then I know that you can tunnel it. I use Giganews, which offers SSL usenet, and I use NN with it via stunnel. Aaron W. Hsu -- A professor is one who talks in someone else's sleep.
From: Aaron W. Hsu on 14 Dec 2009 22:28 Peter Chant <peteRE(a)MpeteOzilla.Vco.ukE> writes: >andrew wrote: >> As a sidenote here not many people realise how truly flexible slrnpull >> and slrn can be: >> >> http://www.andrews-corner.org/usenet/slrnpull.png >I assume if you find slrn too bloaty you can read the news spool using >less.... If SLRN/pull is too much for you, the NN/nnmaster is probably the next one to try. ;-) Aaron W. Hsu -- A professor is one who talks in someone else's sleep.
From: Sidney Lambe on 14 Dec 2009 22:44 On alt.os.linux.slackware, barnabyh <invalid(a)address.org> wrote: > Ewald Pfau wrote: > >> When using software, which does not need a server, as >> slrn or tin, you may access the news-spool directly (in >> /var/spool/news) and exchange news with slrnpull, part of >> slrn. >> >> For tin, I use three lines for bash, acting as 'inews' program >> (configured as 'inews_prog' for tin): > > Didn't get tin to work with this particular server, I think > it's because it does not support snews. > > >> #!/bin/sh out="/var/spool/slrnpull/out.going" tt=$(mktemp >> /tmp/XXXXXX); ts=$out/X${tt#/tmp/}.news; mv $tt $ts; while >> read z; do { echo $z >>$ts; } done >> >> Switching from unmaintained 'suck' (for exchange) and 'snews' >> (as a tiny server), I had minimum effort for 'slrnpull' with >> two paths linked: >> >> /var/spool/slrnpull/news -> /var/spool/news out.going -> >> /var/spool/slrnpull/var/lib/news/out.going > > > Experimenting with slrn now, thanks for the tip. > > Barnabyh Slrn/slrnpull work very well for me. But I don't use nntps and don't know if it supports it. Filtering is very sophisticated, far beyond my simple needs. You only need leafnode if you are going to be pulling from different servers and want one newspool. news.software.readers Sid
From: Robert Komar on 15 Dec 2009 01:34
Sidney Lambe <sidneylambe(a)nospam.invalid> wrote: .... > You only need leafnode if you are going to be pulling from > different servers and want one newspool. Or, if you want a longer expiration time on articles than your newspool provides. Actually, in my case, I started up on dial-up, and didn't want to be off the hook while reading the news. leafnode would suck in the articles in a minute or two, and I could spend much longer than that reading from the local news server. Nowadays, I have broadband, but I like having a guaranteed expiration date on my groups of interest since my reading comes in well-spaced bursts. It took some effort to get leafnode configured way back then, but it has paid off in spades since. Cheers, Rob Komar |