From: news@xenitec.on.ca (xenitec.on.ca News Administrator)
Newsgroups: biz.sco.general
Subject: Re: uugetty problems
Date: 10 Sep 92 01:45:02 GMT
Organization: [resent by] The SCOGEN gateway and Propagation Society
Resent-From: mmdf@xenitec.on.ca
Submit-To: scogen@xenitec.on.ca
Precedence: bulk

Bill Irwin writes:
> jmiller@wendy.bowlgreen.oh.us (Jim Miller) writes:
> 
> :    I was under the impression that uugetty watched for LCK files in
> : /usr/spool/uucp, and if it found a lock for the line it was on, it would step
> : aside. When it noticed that the lock file was gone, it was to start up uuchat
> : and re-initialize the line. Is this correct?
> 
> I have a similar problem, although my SCO UNIX 3.2.2 system
> uugetty never realizes that the modem is in use and never puts a
> LCK file out.  I have set the ownership of /dev/ttyA12 (the modem
> port) to uucp, but after a dialout attempt the ownership is back
> to root:terminal again.
> 
> The port has been configured in the Devices file and the inittab
> has been changed to run uugetty.  I have setup uucp on many SCO
> system and have never had this problem before.  I'm stumped.
> 

Here's a message that Don Draper posted in this place a few months ago:

--begin included posting--

From: Don Draper <dond@sco.COM>
Subject: non-answering modem solution
Date: 	Tue, 5 May 1992 18:26:42 -0400
Organization: The Santa Cruz Operation, Inc.

Here's an easy and little-known solution to a common modem problem.
It took me a long time to solve this one.  Hope it comes in handy
and saves you some of the frustration that this cost me...

After I call out on my modem, it no longer answers the phone.

KEYWORDS: uucp honeydanber devices ttys xenix unix auto answer reinitialize -hflag dialer uuchat not called acu

RELEASE:  SCO XENIX Operating System Release 2.3.0 through 2.3.4
	  SCO UNIX System V/386 Release 3.2 Operating System Version 4.0 and
	  earlier
	  SCO Open Desktop Release 2.0 and earlier

PROBLEM:  My modem isn't being reinitialized for dial-in.  Disabling
	  and re-enabling the port doesn't help.   The modem must be
	  turned off and on before it will answer the phone again.

CAUSE:    Whenever getty (or uugetty) is run, it checks the file
	  /usr/lib/uucp/Devices to see if the tty port it is running
	  on is a modem port.  If it finds the tty device in the Devices
	  file, then getty checks to see if a binary dialer or Dialers 
	  file entry is being used.  If one of these is found, then getty
	  attempts to hang up the modem line and initialize the modem for
	  the next caller.  If a binary dialer is specified on the Devices 
	  file line, then getty calls that dialer with the "-h" flag.  If 
	  a Dialers file entry is specified instead, then getty calls uuchat,
	  passing it the "&" line from the Dialers file entry.

	  getty uses the first entry which it finds in the Devices file.
	  The tty device name is "regularized" (i.e. tty1a and tty1A are
	  considered equivalent).  This means that if an entry such as:

	  Direct tty1a - 2400 direct

	  appears before the ACU entry for the same tty port, such as:

	  ACU tty1A - 2400 hayes2400 \D

	  then getty will decide that no binary dialer or Dialers file
	  entry is being used - and the modem won't be initialized for
	  dial-in.

	  It is worth mentioning here that the device names in both
	  /usr/lib/uucp/Devices and /etc/inittab should not contain
	  the "/dev/" prefix.  For example, "tty1A" should be used;
	  not "/dev/tty1A".  If the tty device appears as "tty1A" in
	  /etc/inittab, and as "/dev/tty1A" in the Devices file, then
	  getty will not find it, and will treat the tty device as
	  a terminal rather than as a modem.

SOLUTION: Make sure that the "ACU" entry for the modem control port
	  in /usr/lib/uucp/Devices contains the desired binary dialer
	  name or Dialers file entry name and appears before any other
	  entries for this port, including any "Direct" entries for the
	  port's non-modem control counterpart.  This "ACU" entry ("ACU"
	  is the typical label, it could have another label such as
	  "RESET") should also specify the correct speed for 
	  reinitializing the modem.

-
Don Draper		Support Engineer
dond@sco.COM	 Modem Technical Feature Specialist
uunet!sco!dond	 The Santa Cruz Operation, Inc.

--end included posting--

See if that helps.
JP

-- 
Jean-Pierre Radley   Unix in NYC   jpr@jpr.com   jpradley!jpr   CIS: 72160,1341
Newsgroups: biz.sco.general