:Hi, thanks to all who have thus far answered my origional post.
:Unfortunately, as I retrieve my news from an NNTP server outside my network,
:I have no control over how many connections it can handle ETC... If someone
:on my network reads news with NetScape, or lynx, there is no delays; this
:only seems to happen with UQWK or tin.
Have you considered using 'at' to schedule the bundling of your news
and mail? For me it has overcome the problem of long waits for uqwk
to communicate with the news server. Most unices have 'at' available,
though not all services will enable it for users. See the man page for
correct 'at' syntax and/or contact your sysadmin.
Here's the shell script I use :
#!/bin/sh
# package news/mail using an at job - modify the variables to suit
# your setup
UQ_READ_ONLY=0
UQ_HOME_DIR=$HOME
UQ_NRC_FILE=$HOME/t_newsrc.yes
NNTPSERVER=news.ark.com
INEWS_PATH=/usr/bin/inews
UQ_MAX_BLKS=16000
export UQ_READ_ONLY UQ_HOME_DIR UQ_NRC_FILE UQ_MAX_BLKS NNTPSERVER INEWS_PATH
# Make sure we're where we're supposed to be on the disk:
cd
# Check for existence of a previous news file:
if [ -f "$HOME/newnews.zip" ]
then
mv newnews.zip lastnews.zip
fi
uqwk2 -m +n +x +L -Nt_newsrc.yes
zip newnews *.MSG AREAS
rm *.MSG AREAS
# That's it - end of soup_at
From the shell prompt, I use at to schedule the job :
~mars: at 0530 -f bin/soup_at
This simply runs the shell script 'soup_at', at 5:30 am. When I call
in the morning I download newnews.zip ...