Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!bloom-beacon!tut.cis.ohio-state.edu!cs.utexas.edu!sun-barr!texsun!pollux!killer!kcdev!gentry
From: gentry@kcdev.UUCP (Art Gentry)
Newsgroups: comp.mail.uucp
Subject: Re: Concurrent uucico with mutiple dialout modems
Summary: modify Maxuuscheds
Message-ID: <788@kcdev.UUCP>
Date: 22 Jun 89 13:36:09 GMT
References: <43f28c84.f81c@gtephx.UUCP>
Organization: AT&T Kansas City, MO.
Lines: 21

In article <43f28c84.f81c@gtephx.UUCP>, barriost@gtephx.UUCP (Tim Barrios) writes:
> [problem intro vergage deleted]
> 
> We can obvoiusly make this work by doing our own concurrent uucico sessions
> from some kind of home-grown script but we would prefer to let uusched
> do it.  It makes a lot of sense for uusched to be able to do concurrent
> uucico sessions when multiple dialout modems are available.  I must be
> doing something wrong.  Can someone tell me what it is?
> 
In the directory /usr/lib/uucp are several Max* files.
The file Maxuuscheds defines the maximum number of concurrent uuscheds allowed.
The file Maxuuxqts defines the maximum number of concurrent uuxqts.

On all of my AT&T 3B systems, the default as delivered was 1 in each.


-- 
| R. Arthur Gentry     AT&T Communications     Kansas City, MO     64106 |
| Email: killer!kcdev!gentry         ATTMail: attmail!kc4rtm!gentry      |
| The UNIX BBS: 816-221-0475         The Bedroom BBS: 816-637-4183       |
| $include {std_disclaimer.h}        "I will make a quess" - Spock - STV |