I am putting the finishing touches on an Ubuntu wiki page for slrn:
https://help.ubuntu.com/community/slrn
but I have hit a small snag with the slrnpull section:
https://help.ubuntu.com/community/slrn#Using%20slrnpull
Despite specifying the NNTPSERVER variable in ~/.bashrc (which slrn
itself reads well enough) slrnpull does not read the variable and the
server needs to be specified on the commandline, as described in the
wiki.
This is the slightly older slrn version of Karmic Koala:
#v+
andrew@skamandros:~$ slrn --version
slrn pre1.0.0-11
* Note: This version is a developer preview.
S-Lang Library Version: 2.1.4
Compiled at: Jun 15 2009 14:44:11
Operating System: Linux
andrew@skamandros:~$ slrnpull --version
12/12/2009 18:58:13 ***slrnpull version: pre1.0.0-11
#v-
I have a feeling I am missing something basic here and I will be more
than happy to have my nose rubbed in it :).
Andrew
--
Do you think that's air you're breathing?
> Despite specifying the NNTPSERVER variable in ~/.bashrc (which slrn
> itself reads well enough) slrnpull does not read the variable and the
> server needs to be specified on the commandline, as described in the
> wiki.
Or more correctly it reads the variable as an ordinary user but not when
using sudo.
That's not a slrnpull problem, but rather a sudo environment issue. I
believe sudo only uses a small set of environment variables for security
reasons. See http://www.gratisoft.us/sudo/man/sudo.html#environment
Your best bet may be to have sudo call a wrapper script that sets the
NNTPSERVER variable and starts slrnpull.
- W. Citoan
--
This is supposed to be a happy occasion. Let's not bicker and argue about
who killed who.
-- Monty Python
> That's not a slrnpull problem, but rather a sudo environment issue. I
> believe sudo only uses a small set of environment variables for security
> reasons. See http://www.gratisoft.us/sudo/man/sudo.html#environment
>
> Your best bet may be to have sudo call a wrapper script that sets the
> NNTPSERVER variable and starts slrnpull.
OIC, I suspect you are perfectly correct. Since this is simply a setup
guide I shall leave the commandline usage in place and mention
possibilities of scripts + cron...