From owner-freebsd-current  Thu Jul 18 14:04:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA17555
          for current-outgoing; Thu, 18 Jul 1996 14:04:34 -0700 (PDT)
Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA17546
          for <current@FreeBSD.org>; Thu, 18 Jul 1996 14:04:31 -0700 (PDT)
Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id QAA08043; Thu, 18 Jul 1996 16:02:49 -0500
From: Joe Greco <jgreco@brasil.moneng.mei.com>
Message-Id: <199607182102.QAA08043@brasil.moneng.mei.com>
Subject: Re: various 'fetch' errors
To: imp@village.org (Warner Losh)
Date: Thu, 18 Jul 1996 16:02:49 -0500 (CDT)
Cc: jlemon@americantv.com, current@FreeBSD.org
In-Reply-To: <199607182004.OAA02779@rover.village.org> from "Warner Losh" at Jul 18, 96 02:04:24 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> : 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

In reality, one might want the ability to specify a "max concurrent xfers"
limit.  Old SunOS cron did this (I think Solaris does too), one could specify
how many jobs of a given grade would be run simultaneously.  (see man 5
queuedefs).

Probably long forgotten except by us old Sun3 performance tuning freaks.

a.4j1n
b.2j2n90w
n.1j10n60w

Ah, the old days.

Anyways, that sort of functionality would allow those of us with high 
speed connectivity to live happy, while still allowing for the slow 14.4K
link folks who are interested in scheduling transfers while they are not
using their machines.

... JG