[rc5] Best setup for infrequent dial-up connection
slim at ipapilot.org
Sun Oct 26 01:22:10 EST 1997
So if dial-on-demand is installed, there's no way to have the client look
for an existing dial-up connection without making one itself. What I'm
trying to avoid is saying, "Okay, Mom, now what you want to do is open a
command line and flush and refill your buffers with the -update switch." I
realize I could set up a shortcut or something, but ideally I'd like to
make it *completely* transparent. There are a bunch of computers I could
run this on if it required absolutely nothing from the computer's owner.
I'd let them know what it was and what it did, but I wouldn't expect them
to do anything in the way of maintenance or allow it to be at all
intrusive, by making unexpected dial-up connections for example.
From: Tim Charron <tcharron at interlog.com>
To: rc5 at llamas.net <rc5 at llamas.net>
Date: Sunday, October 26, 1997 12:51 AM
Subject: Re: [rc5] Best setup for infrequent dial-up connection
> There's been some mention of -frequent and -runoffline command-line
> switches, some combination of which may accomplish what I'm trying to
> but they don't appear to be documented anywhere. Can someone shed some
This is pretty weak in terms of documentation, but until a client faq
'rc564 help' will give a quick list of command line options. Most
of the options correspond to those configurable via 'rc564 -config'.
Other options of interest are:
-runoffline: Never try to access the network for fetches/flushes
when buffers are empty, generate random ones.
(useful for non-connected clients, or when sharing buffers)
-runbuffers: Like -runoffline, but when the current input buffer
is empty, quit.
-frequent: This will make the client perform an update every couple
of minutes. If dial-on-demand is not installed, then
this is the best way to automatically take advantage of
an occassional network connection.
-nodisk: No buffer files are saved on disk. Everything is held
in memory. This will allow hard disks to go into power
-nofallback: Usually, after failed server connection attempts, an
attempt to rc5proxy.distributed.net will be made. This
will disable this behaviour.
-forceunlock:It is possible for a buffer to become locked permanently
if the client should crash while the buffer is locked.
This option will force the buffer to be unlocked.
To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5'
in the body.
To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5' in the body.
More information about the rc5