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
LEARN ABOUT FREEBSD
fuser
FUSER(1) BSD General Commands Manual FUSER(1)
NAME
fuser -- list IDs of all processes that have one or more files open
SYNOPSIS
fuser [-cfkmu] [-M core] [-N system] [-s signal] file ...
DESCRIPTION
The fuser utility writes to stdout the PIDs of processes that have one or more named files open. For block and character special devices,
all processes using files on that device are listed. A file is considered open by a process if it was explicitly opened, is the working
directory, root directory, jail root directory, active executable text, kernel trace file or the controlling terminal of the process. If -m
option is specified, the fuser utility will also look through mmapped files.
The following options are available:
-c Treat files as mount point and report on any files open in the file system.
-f The report must be only for named files.
-k Send signal to reported processes (SIGKILL by default).
-m Search through mmapped files too.
-u Write the user name associated with each process to stderr.
-M Extract values associated with the name list from the specified core instead of the default /dev/kmem.
-N Extract the name list from the specified system instead of the default, which is the kernel image the system has booted from.
-s Use given signal name instead of default SIGKILL.
The following symbols, written to stderr will indicate how files is used:
r The file is the root directory of the process.
c The file is the current workdir directory of the process.
j The file is the jail-root of the process.
t The file is the kernel tracing file for the process.
x The file is executable text of the process.
y The process use this file as its controlling tty.
m The file is mmapped.
w The file is open for writing.
a The file is open as append only (O_APPEND was specified).
d The process bypasses fs cache while writing to this file (O_DIRECT was specified).
s Shared lock is hold.
e Exclusive lock is hold.
EXIT STATUS
The fuser utility returns 0 on successful completion and >0 otherwise.
EXAMPLES
The command: ``fuser -fu .'' writes to standard output the process IDs of processes that are using the current directory and writes to stderr
an indication of how those processes are using the directory and user names associated with the processes that are using this directory.
SEE ALSO
fstat(1), ps(1), systat(1), iostat(8), pstat(8), vmstat(8)
STANDARDS
The fuser utility is expected to conform to IEEE Std 1003.1-2004 (``POSIX.1'').
HISTORY
The fuser utility appeared in FreeBSD 9.0.
AUTHORS
The fuser utility and this manual page was written by Stanislav Sedov <stas@FreeBSD.org>.
BUGS
Since fuser takes a snapshot of the system, it is only correct for a very short period of time. When working via kvm(3) interface the report
will be limited to filesystems the fuser utility knows about (currently only cd9660, devfs, nfs, ntfs, nwfs, udf, ufs and zfs).
BSD
May 13, 2011 BSD