Re: Where should groups.dat be located?

Patrick Shanahan wrote:
> * Larry Alkoff <[email protected]> [06-06-07 15:33]:
>  [...]
>>> slrn -f ~/.newsrc -i ~/.slrnrc -C -h news-server.indy.rr.com --create
>>>
>>> then
>>>
>>> slrn -f ~/.rrnewsrc -i ~/.slrnrc -C -h news-server.indy.rr.com
>>>
>> Thanks for the help Patrick.
>>
>> I have sucessfully created a ~/.newsrc from your --create line above
>> and subscribed to a single newsgroup.  A nice step forward.
>>
>> What does the second line containing 'rrnewsrc' do?
> 
> an error in my part for the example, s/b ".newsrc".
> Explanation:  I have several scripts to different nntpsources, ie:
> slrn.rr, that allow me to not type the entire cl line for access.  The
> prepended rr defines news-server.indy.rr.com.
> 
>>  From my reading, the next step would be to get the headers for which I 
>> have customized a 'slrnpull.sh' script from someone else.
>>
>> Would you please give it a sanity check?
>>
>>
>> #!/bin/sh
>>
>>
>> dir=/var/spool/slrnpull/news
>> server=news.west.earthlink.net
>>
>> # I'm not sure what to put in the next line:
>> # ?? slrnpull=/home/john/src/slrn/src/objs/slrnpull
> 
> looks like the route to the executable, slrnpull.  put the output from
>     which slrnpull
> there.  For me it would be "slrnpull=/usr/bin/slrnpull"    
> 
>> umask 022
>>
>> # Before getting new articles, perform expiration.
>> $slrnpull -d $dir --expire
>>
>> # I don't think this last line is working and don't understand
>> 'perform expiration'.   Will I die?
> 
> per TFM, --expire      Expire (remove) old messages from the spool, but do
>                        not fetch news.
> 	      
> you *really* would benefit from reading the manuals, "man slrn" and
> "man slrnpull" and looking at the command-line helps, "slrn[pull] --help"
> and comparing the examples included with the distribution:
> 
> /usr/share/doc/packages/slrn/slrnpull/README
> /usr/share/doc/packages/slrn/slrnpull/README.offline
> /usr/share/doc/packages/slrn/slrnpull/SETUP
> /usr/share/doc/packages/slrn/slrnpull/score
> /usr/share/doc/packages/slrn/slrnpull/setgid.txt
> /usr/share/doc/packages/slrn/slrnpull/slrn.rc
> /usr/share/doc/packages/slrn/slrnpull/slrnpull.conf
> /usr/share/doc/packages/slrn/slrnpull/slrnpull.sh
> 
> 
> btw, if you are not on dial-up, slrnpull is rather excessive.
> 


Again thanks for your help Patrick.

I have been reading and re-reading the files you mention for several 
days.  But I've found in Linux sometimes the meaning of config options 
is not apparent until I finally stumble on the right combination.  After 
that, it's easy <g>  I used Slackware for years so I don't mind RTFMing.

 From my reading, you need slrnpull to retain headers and messages on 
disk.  I'd be happy to not use slrnpull but want all the information I 
download to stay on disk until I tell it to go away.  Can slrn alone do 
that?

Possibly I've gotten bad habits from years of using Forte Agent under 
wine where you have to explicitly delete a post or header.  Problem is 
I'm tired of messing with wine each time I install just to run Agent.

Larry



-- 
Larry Alkoff N2LA - Austin TX
Using Thunderbird on Linux

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/