ktrace(2) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

ktrace(2)

The  system  call  enables  or  disables  tracing  of one or more
processes.  Users may only trace their own processes.   Only  the
super-user  can  trace  setuid  or setgid programs.  The argument
gives the pathname of the file to be used for tracing.  The  file
must exist and be a regular file writable by the calling process.
All  trace  records  are always appended to the file, so the file
must be truncated to zero length to discard previous trace  data.
If tracing points are being disabled (see KTROP_CLEAR below), may
be  NULL.  The argument specifies the requested ktrace operation.
The defined operations are: specified process and all its current
children.  The argument specifies the trace points  of  interest.
The  defined trace points are: generate much output).  Each trac‐
ing event outputs a record composed of a generic header  followed
by  a  trace  point  specific  structure.  The generic header is:
struct                        ktr_header                        {
        int             ktr_len;                /*  length of buf
*/            short           ktr_type;               /*    trace
record type */         pid_t           ktr_pid;                /*
process  id */         char            ktr_comm[MAXCOMLEN+1];  /*
command            name             */                     struct
timeval  ktr_time;               /*          timestamp         */
        intptr_t        ktr_tid;                /* was ktr_buffer
*/ }; The field specifies the length of  the  data  that  follows
this header.  The and fields specify the process and command gen‐
erating  the  record.  The field gives the time (with microsecond
resolution) that the record was generated.   The  field  holds  a
thread  id.  The generic header is followed by bytes of a record.
The type specific records are defined in the include  file.   The
following  tunables  influence the behaviour of bounds the amount
of data a traced I/O request will log to the trace file.   bounds
the  number  of trace events being logged at a time.  Sysctl tun‐
ables that control process debuggability (as determined  by  also
affect the operation of The system call will fail if: A component
of the path prefix is not a directory.  A component of a pathname
exceeded  255  characters,  or  an entire path name exceeded 1023
characters.  The named tracefile does not exist.  Search  permis‐
sion is denied for a component of the path prefix.  Too many sym‐
bolic links were encountered in translating the pathname.  An I/O
error  occurred while reading from or writing to the file system.
The kernel was not compiled with support.  A thread may be unable
to log one or more tracing events due to a temporary shortage  of
resources.   This  condition is remembered by the kernel, and the
next tracing request that succeeds will have the flag set in  its
field.  The system call first appeared in






















맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3