Hello,

We have some problem when we try to access terminal concentrator
from sun V480. We have configure the /etc/remote file like this way:

hardwire:\
        :dv=/dev/term/a:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:

When we enter the command tip hardwire we always get this messages:
tip: /dev/term/a: Permission denied
all ports busy

We also try also to change the configure of serial ports with admintool but
it 's say
configuration change failed.

Any idea
Thanks

mika wrote:
> Hello,
> 
> We have some problem when we try to access terminal concentrator
> from sun V480. We have configure the /etc/remote file like this way:
> 
> hardwire:\
>         :dv=/dev/term/a:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
> 
> When we enter the command tip hardwire we always get this messages:
> tip: /dev/term/a: Permission denied
> all ports busy
> 
> We also try also to change the configure of serial ports with admintool but
> it 's say
> configuration change failed.
> 
> Any idea
> Thanks

OK, so you are trying to access the terminal concentrator from the Sun 
V480 serial port?  Is that so you can connect to the t/c console port 
for configuration purposes?

The error message you are getting means that something else is using the 
serial port (all ports busy) and that the devices don't have the propoer 
permissions (permission denied)

The V480 should be using serial port a as it's console which probably 
explains the "all ports busy" i.e. the console process has the port and 
tip can't use it. (if you have configured the RSC card as the console, 
this wouldn't apply.)

Also, when using the "hardwire" line in the /etc/remote file, change 
/dev/term/a to /dev/cua/a.  Also, the character device files that the 
links in /dev/term and /dev/cua are pointing to should be owned by tty 
and uucp respectively.

You shouldn't have any service running on port a in admintool.  If you 
do, remove it so it says "no service".  Also, if your serial port a IS 
the console, you can't use it for anything else.  You may want to use 
another machine to configure the t/c, if that is what you are doing.  If 
you are just trying to connect the v480 serial port a console to the 
t/c, you don't have to use tip for anything.  Just make sure you have 
the proper cabling and plug it in..

correction:

both sets of character device files for the cua and term devices should 
be owned by uucp.

ML Starkey <martha.starkey@sun.com> writes:
>correction:
>
>both sets of character device files for the cua and term devices should 
>be owned by uucp.
>

No, the term devices are owned by root.  Ttymon will change the ownership
if it's run on the devices and finds them owned by someone else.  Ttymon
runs as root, so it can open the root owned device files in /dev/term.
Only the cua devices are owned by uucp, so uucp utilities (uucico, cu) can
open them for dial-out purposes.  Tip and kermit are suid uucp, just like
cu, so they also can open the device files in /dev/cua for dial-out purposes.

  -Greg
-- 
Do NOT reply via e-mail.
Reply in the newsgroup.

Approximately 8/20/03 06:16, mika uttered for posterity:

> Hello,
> 
> We have some problem when we try to access terminal concentrator
> from sun V480. We have configure the /etc/remote file like this way:
> 
> hardwire:\
>         :dv=/dev/term/a:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
> 
> When we enter the command tip hardwire we always get this messages:
> tip: /dev/term/a: Permission denied
> all ports busy

   Best advice is to head for Stokely and run thru their tutorial
   information on the serial ports.

   If something else has already opened that port, you won't be
   able to use it.  Can be checked with pmadm and/or ps -*** | grep
   term.   Normally term/a isn't there until someone or something
   has pushed a tty driver on the port if memory serves.  Can
   be tested with "stty -a < /dev/term/a"

   When I run tip, I normally use the cu device, as tip does not
   require that the portmonitor be enabled on the port, or that
   the port be properly configured in /etc/uucp/Devices or
   /etc/uucp/Dialers.

   # tip /dev/cua/a

   For debugging, 'cu' is better IMNHO, as it has debug mode
   available.  See below.
> 
> We also try also to change the configure of serial ports with admintool but
> it 's say
> configuration change failed.

  Another symptom the port is in use.

[CAUTION] below is for a slightly different purpose, however, you
          should be able to merge it and the man pages to debug
          your issue, particularly after visiting the Stokely site.

The standard uucp configuration files do not have entries for port ttya.
This will cause cu to fail:
# /usr/bin/cu -l /dev/cua/a
Connect failed: NO DEVICES AVAILABLE

The debug mode of cu shows the problem:
# cu -d -l /dev/cua/a
altconn called
Device Type Direct wanted <== no "Direct" in /etc/uucp/Devices
Requested Device Type Not Found
getto ret -1
Connect failed: NO DEVICES AVAILABLE
call cleanup(1)
call _mode(0)

File /etc/uucp/Devices must have entries (typically at the bottom) for
/dev/cua/a and /dev/cua/b:

/etc/uucp/Devices:
ACU cua/b - Any hayes [not needed]
Direct cua/b - Any direct
#
ACU cua/a - Any hayes
Direct cua/a - Any direct

The debug mode of cu also shows the missing entry from /etc/uucp/Dialers:

# cu -d -l /dev/cua/a
altconn called
Device Type Direct wanted
Trying device entry 'cua/a' from '/etc/uucp/Devices'. <== device exists
Devices file OK
processdev: calling setdevcfg(cu, Direct)
fd_mklock: ok
fixline(5, 9600)
gdial(direct) called
direct not found in Dialers file <== no "direct" in /etc/uucp/Dialers
set interface UNIX
getto ret -1
Connect failed: CAN'T ACCESS DEVICE
call cleanup(1)
call _mode(0)

File /etc/uucp/Dialers must have a "direct" entry. This is just the
single, uncommented, word "direct" on a line by itself:


/etc/uucp/Dialers:
micom "" "" \s\c NAME? \D\r\c GO
direct
##########

Yes greg,

You have right

Thanks for your answer

"Greg Andrews" <gerg@panix.com> a �crit dans le message de
news:bi0tmc$5q0$1@reader2.panix.com...
> "mika" <hakzia@hotmail.com> writes:
> >Hello,
> >
> >We have some problem when we try to access terminal concentrator
> >from sun V480. We have configure the /etc/remote file like this way:
> >
> >hardwire:\
> >        :dv=/dev/term/a:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
> >
> >When we enter the command tip hardwire we always get this messages:
> >tip: /dev/term/a: Permission denied
> >all ports busy
> >
>
> Have you configured the V480 to have its console on the ttya
> port instead of the RSC card?  If so, the serial port is only
> available to the console, and not to tip.
>
>   -Greg
> -- 
> Do NOT reply via e-mail.
> Reply in the newsgroup.