[comp.sys.ncr] UUSCHED DOUBLES UP

nigel@cmsfl@labtam.oz (Nigel Harwood) (02/09/90)

Yep ... I'm still mucking about trying to get my HDB UUCP working
with multiple lines.

Scenario: Tower 32/650 UNIX 020101, HDB UUCP and 10 outgoing lines.

I have a uusched being spawned every 3 minutes by uucp cron so that
all the MODEMS can be driven as hard as possible i.e. a lot of short
transmissions.

The problem is that it appears uusched looks at the queued jobs before
it starts and doesn't check them again before it fires of uucico.

In other words one uusched will start and see that system abc needs
talking to so fires off a uucico.

Mean while another uusched starts up and starts looking through the
jobs.

The first uucico finishes.

The second uusched doesn't look and see abc has been done and starts
another uucico to it.

It seems that a) uusched doesn't verify jobs after its initial pass and
b) the very large number of systems (>350) is causing a delay which
is exaserbating the problem.

What does anyone else think ?

BTW. Thanks to all the people who answered my other questions.  This
	  is by far the most responsive news group I have dealt with.

-- 
<<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>
<< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >>
<< Phone: +61 3 829 6090      E-mail: nigel%cmsfl@labtam.oz.au >>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

wescott@Columbia.NCR.COM (Mike Wescott) (02/11/90)

In article <356@cmsfl> nigel@cmsfl@labtam.oz (Nigel Harwood) writes:
> The problem is that it appears uusched looks at the queued jobs before
> it starts and doesn't check them again before it fires of uucico.

$%*+@#! We fixed this problem once several releases ago.  Looks like
the fix got lost.  I still maintain that uusched ought to be completely
rewritten but in the meantime there will have to be a simpler solution
to Nigel's problems.

	
--
	-Mike Wescott
	 mike.wescott@ncrcae.Columbia.NCR.COM