From owner-freebsd-current  Thu Jul 18 13:04:56 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA13200
          for current-outgoing; Thu, 18 Jul 1996 13:04:56 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA13193
          for <current@freebsd.org>; Thu, 18 Jul 1996 13:04:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id OAA02779; Thu, 18 Jul 1996 14:04:24 -0600 (MDT)
Message-Id: <199607182004.OAA02779@rover.village.org>
To: Jonathan Lemon <jlemon@americantv.com>
Subject: Re: various 'fetch' errors 
Cc: current@freebsd.org
In-reply-to: Your message of Thu, 18 Jul 1996 13:01:39 CDT
Date: Thu, 18 Jul 1996 14:04:24 -0600
From: Warner Losh <imp@village.org>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

: > Heck, I'd be happy with a lpr-like interface to fetch.  If there was a
: > fetchd running in the background, and I said "fetch --background
: > ftp://ftp.x.org/pub/R6.1/tars/xc-1.tar.gz --after tomorrow" it would
: > queue the file for fetching and let me knwo when it is done.  That way
: > I could queue up 20-30 things to get and then go to sleep.  I've
: > wanted this feature in an FTP program for a long time and have *NEVER*
: > seen one with it.[*]
: 
: Maybe I'm being naive, but wouldn't "at 1am + 2 days fetch ftp://...." do
: what you want?

Yes.  You are being naive.  :-) Let's say I wanted to fetch 10-20
things.  And I have microbandwidth to the rest of the world.  I want
them to happen sequentially rather than in parallel.  Let's also say I
have multiple users that want to do this (say 1-2 each and there are 5
of them), then the savings really kicks in because the files will then
get transferred and there will be some chance at getting some
bandwidth for interactive jobs.

Warner