Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!wuarchive!mit-eddie!uw-beaver!Teknowledge.COM!unix!hplabs!hpfcso!stroyan
From: stroyan@hpfcso.HP.COM (Mike Stroyan)
Newsgroups: comp.sys.hp
Subject: Re: HP 360 communication problems
Message-ID: <7370108@hpfcso.HP.COM>
Date: 19 Mar 90 23:34:17 GMT
References: <4933@utastro.UUCP>
Organization: Hewlett-Packard, Fort Collins, CO, USA
Lines: 29

> system, when any X windows activity occurs.  To limit our losses, a front-end
> buffering program is executed with real-time priority 0 and is locked into
> memory.  X windows is run at real-time priority 10.  This has prevented 
> character loss, but the performance of X and analysis tasks are then
> unacceptable.

You might get better performance by running the X server at normal
priority.  The real time priority may have the X server handling client
requests in very small groups of requests.  There is some amount of
fixed overhead in handling a group of requests.  If there is a large
number of small groups then the total overhead increases.  This could
give lower throughput than a normal priority server handling larger
buffers.

> 2) We wish to exchange data with a central location via modems (not the same
> port as in 1) above) and have acquired a pair of Racal-Vadic (sp?) 9600 baud
> modems to test the setup.  The problem is that if one uses cu, kermit
> or anything to call out or just talk to the modem (on ttyd01) from the HP, 
> then subsequent incoming calls are not handled properly.  The incoming call 
> is answered and connected, but there is no login prompt.  Turning the modem 

>                        Randy Ricklefs

Use uugetty on the modem rather than a normal getty.  See the uugetty
man page and the UUCP tutorial in "HP-UX Concepts and Tutorials" for
more information.  (I don't actually have to deal with UUCP myself, but
this is a problem that I have seen others run into and comment on.)

Mike Stroyan, stroyan@hpfcla.hp.com