Re: [leafnode] Instant Upload
- From: Blinky the Shark <no.spam@xxxxxxxxxxx>
- Date: 28 Sep 2007 19:24:39 GMT
Peter J Ross wrote:
In news.software.readers on 28 Sep 2007 10:46:33 GMT, Blinky the Shark
<no.spam@xxxxxxxxxxx> wrote:
Peter J Ross wrote:
In news.software.readers on 28 Sep 2007 09:56:01 GMT, Blinky the Shark
<no.spam@xxxxxxxxxxx> wrote:
Peter J Ross wrote:
In news.software.readers on Fri, 28 Sep 2007 00:25:15 +0200, Robert
Spanjaard <spamtrap@xxxxxxxxxx> wrote:
On Thu, 27 Sep 2007 21:21:53 +0000, Blinky the Shark wrote:
Is there a way to get leafnode to upload a post when I send it from my
client, so it doesn't have to wait until the next leafnode cron job?
If it's possible, you should edit inetd.conf and replace the execution of
leafnode by a script which executes leafnode followed by fetchnews -P
(=post only). But I'm not sure if inetd allows the use of scripts.
Looking at this again, I suspect that it may not work, since
"fetchnews -P" will attempt to start leafnode, which has been replaced
in inetd.conf by a script.
If it doesn't work, you could setup a new cron job which executes
fetchnews -P every 5 minutes, for example.
... but not when a full fetchnews is scheduled to run, or you'll get
harmless but annoying error messages.
Another possible solution would be a shell script that looks at
/var/spool/news/out.going/ and runs fetchnews -P if the directory
isn't empty and fetchnews isn't already running. Run the script with
cron every minute or every 30 seconds.
And thank you, too, Peter. My nature makes me want to do whichever of
those more efficient (assuming same frequency). Seems offhand like that
would be yours, in that it doesn't involve fetchnews unless there's
reason. Comments?
Frequency affects efficiency. There's a limit to how often you can run
fetchnews without bumping into a fetchnews that's already running,
which is why I suggest checking whether there are any articles waiting
to be posted before doing anything.
Run "newsq -c".
If exit status is 0, see if a fetchnews process is running.
If not, run "fetchnews -P".
Ah! I wasn't expecting to see headers. :)
<...>
Never got anything about exit status.
With Leafnode 2, newsq -c reports a different exit code depending on
whether there are outgoing posts waiting or not, which is useful for
scripting. It seems that you can't do that with Leafnode 1, which
means that your script will need to be more complicated.
Okay
# newsq -V
newsq 2.0.0.alpha20070602a
# newsq -h
Usage:
newsq [OPTIONS] [-cf]
options are:
-d spooldir - use spooldir instead of compiled-in default
-D debug - set debug flags (see config.example for documentation)
-e - redirect logging to standard error
-F config - read config file as configuration instead of default
-v [...] - increase verbosity level (can be repeated)
-V - just print version and exit, perform no other operation
-c - exit with code 1 on error,
exit with code 0 if out.going queue has articles
exit with code 69 if out.going queue is empty.
-f - print queue of articles to be fetched in delaybody mode
-h - print short usage help like this
Usage: fetchnews [-q] [-v] [-x #] [-l] [-n] [-f] [-P] [-w]
-q: quiet, suppress some warnings, cancels -v
-v: more verbose (may be repeated), cancels -q
-x: check for # extra articles in each group
-l: do not use supplementary servers
-n: do not automatically expire unread groups
-f: force reload of groupinfo file
-P: only post outgoing articles, don't fetch any
-w: wait, run XOVER updater in foreground
I tried the verbose switch and still nothing other than what I reported
earlier. It was worth a shot.
--
Blinky RLU 297263
Killing all posts from Google Groups
The Usenet Improvement Project moved to this site August 28th:
http://improve-usenet.org
.
- References:
- [leafnode] Instant Upload
- From: Blinky the Shark
- Re: [leafnode] Instant Upload
- From: Robert Spanjaard
- Re: [leafnode] Instant Upload
- From: Peter J Ross
- Re: [leafnode] Instant Upload
- From: Blinky the Shark
- Re: [leafnode] Instant Upload
- From: Peter J Ross
- Re: [leafnode] Instant Upload
- From: Blinky the Shark
- Re: [leafnode] Instant Upload
- From: Peter J Ross
- [leafnode] Instant Upload
- Prev by Date: Re: making posts unreadable for google groupers?
- Next by Date: Re: [leafnode] Instant Upload
- Previous by thread: Re: [leafnode] Instant Upload
- Next by thread: Re: [leafnode] Instant Upload
- Index(es):
Relevant Pages
|
Loading