Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.mail.uucp
Subject: Re: Sun OS 4.1.1 (HDB-BNU) Cant call out ..
Message-ID: <5791@auspex.auspex.com>
Date: 7 Feb 91 18:16:09 GMT
References: <7622@suned1.Nswses.Navy.MIL>
Organization: Auspex Systems, Santa Clara
Lines: 23

>generic open failed, errno = 16

When I find the person who first invented the idea of printing "errno"
as a decimal number and *not* as an error string, I'm going to give him
or her the old Hot Lead Enema....

16 is EBUSY, so apparently the system thinks the "cua0" port is busy. 
One reason why the dialout side of a dialin/dialout device might be busy
is that it really *is* busy, i.e., the dialin device has been opened
successfully.  I presume there's nobody dialed in on that port at the
times this failed (otherwise you wouldn't have found it surprising that
it couldn't call out).  Make sure that the line in "/etc/ttytab" for
"ttyd0" and "ttyd1" does *NOT* have "local" in it; if it does, remove
the "local", and run "ttysoftcar -a", to turn off "soft carrier".

In any case, next time it tries to dial out and fails, try "ps -td0"
if the device was "cua0", or "ps -td1" if it was "cua1".  If "ps" reports
that there was a process attached to "ttyd0" or "ttyd1" (whichever is
the dialin half of the dialout device that it couldn't use), that's the
problem - the device really *is* busy.  The next step is to track down
why it's busy (I suspect it's not something obvious like the modem or
the cable pulling CD permanently up, as that would cause the same
problem under 4.0.3).