07-07-2017
A few other ideas:
- there is only a limited number of ttys. Try the fuser command on all of them to find out which process(es) is(are) using it. The examine the found processes.
- if you feel confident enough you can also use kdb (kernel debugger) to examine the processes properties although you will have to find out the details yourself, i don't have the documentation at hand.
- receiving data from a tty means there has to be a physical serial connection to the server. check that and find out the corresponding tty device to further limit the number of devices to examine if you have physical access to the server.
I hope this helps.
bakunin
Last edited by bakunin; 07-08-2017 at 09:07 AM..
This User Gave Thanks to bakunin For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We're running SCO Unix Openserver 5.05 and I'm having trouble with serial communication between the com2 serial port and a handheld device. Downloading data from Unix to the handheld works perfectly, but the other way around creates a major problem. I don't know whether it's a buffer overflow or... (1 Reply)
Discussion started by: Aretha
1 Replies
2. UNIX for Dummies Questions & Answers
I am having trouble with a device connected through a serial port on my sun workstation ( I am running solaris 7).
The seriel device works on an identical workstation running the same o/s version but when I move it to the initial workstation it doesn't work. I am using an rs232 serial cable and... (1 Reply)
Discussion started by: Henrik
1 Replies
3. Solaris
hi
i am using solaris 9 on sparc .
i was wondering if there was a command to control my serial interface , as to send a signal periodically every interval of time to the input of a 555 timer .
thanks for your help .... (0 Replies)
Discussion started by: ppass
0 Replies
4. Programming
Hello!
Can someone advice me which method I will use if I want to communicate with device via RS232 serial port with this requirements:
1. Serial port is opened in non-canonical mode.
2. All the time I need to check is there something to read.
3. If I have to write something I need to write it... (6 Replies)
Discussion started by: jvrlic
6 Replies
5. AIX
Hi,
How can i configure my modem in AIX thru serial port (sa0-->tty0)
I have two port serial card configured as sa0
I created tty1 which port is tty0 and which port is tty1 how can i know?? (1 Reply)
Discussion started by: pchangba
1 Replies
6. What is on Your Mind?
In our last review post, members reviewed Avatar.
Now, let's discuss Sherlock Holmes. (3 Replies)
Discussion started by: Neo
3 Replies
7. Shell Programming and Scripting
Hi,
I have a external board connected to my serial port. I need to execute "shutdown -r now" command when system boot up. When system boots up it requires a username ans password. Then I need to run my command. I can use rc script but that is rebooting system before it asks for username and... (0 Replies)
Discussion started by: charlie.arya
0 Replies
8. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
9. Solaris
I am using ReflectionX on a windows PC to run an application on a Solaris box. The application uses the serial port and expects a definition like: /dev/ttyb
Is there a way to use the PC serial port through ReflectionX?
PC is running Windows-XP
Solaris Box is:
Sun Microsystems sun4u... (1 Reply)
Discussion started by: deanjennings
1 Replies
10. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
cmx(8) System Manager's Manual cmx(8)
Name
cmx - generic communication exerciser
Syntax
/usr/field/cmx [ -h ] [ -ofile ] [ -tn ] -l line-1 ...
Description
The exerciser will write, read, and validate random data and packet lengths on a given communications line. The line under test must have
a loopback connector attached to the distribution panel or the cable and the line must be disabled in the file and a non-modem line. That
is, the flag must be set to off.
The exerciser runs until or kill -15 pid is sent to the process.
A logfile is made in for you to examine and then remove. If there are errors listed in the logfile, make sure that you check the file,
because that is where the driver and kernel error messages are saved.
You must specify the -l flag followed by the lines to test. The line-n arguments identify the lines to be tested. A maximum of 32 lines
can be tested at any one time. The line-n arguments are specified as names taken from the directory without the letters ``tty''. For
example, if the directory lists tty03, the line argument is 03.
The DEVICES section lists the devices that can be tested.
Restrictions
If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that
need to write into a file system, such as the target file system must be writable by root. Also the directory, in which any of the exer-
cisers are executed, must be writable by root because temporary files are written into the current directory. These latter restrictions
are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of
the restrictions may be overcome by copying the exerciser to another directory and then executing it.
Options
-h Prints help message about this command.
-ofile Save output diagnostics in file.
-tn Run time in minutes (n). The default is to run until a or kill -15 pid is sent to the process.
Restrictions
Pseudo devices (those whose first character after tty is p, q, r, s, t, u) cannot be tested. Neither can lta devices with major #39.
Devices
Use the command on to find out which tty line corresponds to a device line number.
Examples
The following example runs the exerciser for 60 minutes on lines 00, 13, 22, and 32.
% /usr/field/cmx -t60 -l 00 13 22 32
The following example runs the exerciser on lines 11, 42, 45, and 76 in the background until interrupted by a or kill -15 pid.
% /usr/field/cmx -l 11 42 45 76 &
See Also
Guide to System Exercisers
cmx(8)