Tusc is not a third party but more HP's implementation of truss...
(only it is not officially supported...)
I have a copy if you want...
Quote:
TUSC System Call Tracing Tool (for HP-UX)
-----------------------------------------
TUSC is a system call tracing tool written by Chris Bertin for
HP-UX 11.00 (and newer). It is similar to the "truss" utility
used by other UNIX variants, such as Solaris. Both PA-RISC and
IA64 versions are provided.
What does the system call "dup" do?
What is the difference between dup and dup2
I have a fair idea of what it does but I am confused when its coming down to the exact details...
Please help me!:confused: (2 Replies)
open, creat, read, write, lseek and close
Are they all primitive?
:confused:
*Another Question: is there a different between a system call, and an i/o system call? (2 Replies)
Hi,
I'm new to UNIX system calls. Can someone share your knowledge as to how exactly system calls should be executed?
Can they be typed like commands such as mkdir on the terminal itself? Also, are there any websites which will show me an example of the output to expect when a system call like... (1 Reply)
I am new to scripting in Perl so I have a dumb question.
I know I can call system commands using
system("date");
But I am not able to:
1. set its output to a variable
2. run in quiet mode(no output to the screen)
The examples i have
#!/usr/bin/perl
print `date +\%y\%m\%d.\%H\%M`;... (5 Replies)
Hello,
how would i be able to call ps in C programming?
thanks,
---------- Post updated at 01:39 AM ---------- Previous update was at 01:31 AM ----------
here's the complete system call, ps -o pid -p %d, getpit() (2 Replies)
Discussion started by: l flipboi l
2 Replies
LEARN ABOUT OSF1
trpt
trpt(8) System Manager's Manual trpt(8)NAME
trpt - Transliterates protocol trace
SYNOPSIS
trpt [-afjst] [-p address]
FLAGS
Print the values of the source and destination addresses for each packet recorded, in addition to the normal output. Follows the trace as
it occurs, waiting briefly for additional records each time the end of the log is reached. Lists the protocol control block addresses for
which trace records exist. Shows only trace records associated with the protocol control block specified in hexadecimal by the address
variable.
You must include a space between the -p flag and the address variable when you specify this flag. Prints a detailed description of
the packet-sequencing information, in addition to the normal output. Prints the values for all timers at each point in the trace,
in addition to the normal output.
DESCRIPTION
The trpt command, used for debugging sockets, queries the buffer of Transmission Control Protocol (TCP) trace records. The TCP trace
record buffer is created when a socket is marked for debugging with the setsockopt(2) subroutine. The trpt command queries the buffer and
then prints a description of the trace records.
When you specify no options, the trpt command prints all the trace records found in the system and groups them according to their TCP/IP
connection Protocol Control Block (PCB).
If you are debugging a system file other than the default, the system argument can be used to replace the default.
Before you can use the trpt command, you must do the following: Isolate the problem and mark for debugging the socket or sockets involved
in the connection. Find the address of the protocol control blocks associated with these sockets by using the netstat -aA command. Then,
you can run the trpt command, using the -p flag to supply the associated protocol control block addresses. You can specify multiple -p
address flags with a single trpt command.
The -f flag can be used to follow the trace log once it is located. The -j flag can be used to check for the presence of trace records for
the socket in question.
If the system image does not contain the proper symbols to find the trace buffer, the trpt command cannot succeed.
FILES
Specifies the command path
RELATED INFORMATION
Commands: netstat(1)
Functions: setsockopt(2) delim off
trpt(8)