CDE/cde/doc/C/guides/man/man6/ttsnoop.sgm

<!-- $XConsortium: ttsnoop.sgm /main/8 1996/09/08 20:01:55 rws $ -->
<!-- (c) Copyright 1995 Digital Equipment Corporation. -->
<!-- (c) Copyright 1995 Hewlett-Packard Company. -->
<!-- (c) Copyright 1995 International Business Machines Corp. -->
<!-- (c) Copyright 1995 Sun Microsystems, Inc. -->
<!-- (c) Copyright 1995 Novell, Inc. -->
<!-- (c) Copyright 1995 FUJITSU LIMITED. -->
<!-- (c) Copyright 1995 Hitachi. -->

<RefEntry Id="CDEMX.MAN109.rsml.1">
<RefMeta>
<RefEntryTitle>ttsnoop</RefEntryTitle>
<ManVolNum>demos</ManVolNum>
</RefMeta>
<RefNameDiv>
<RefName><Command>ttsnoop</Command></RefName>
<RefPurpose>send and receive ToolTalk messages interactively
</RefPurpose>
</RefNameDiv>
<!-- $XConsortium: ttsnoop.sgm /main/8 1996/09/08 20:01:55 rws $-->
<!-- (c) Copyright 1993, 1994 Hewlett-Packard Company-->
<!-- (c) Copyright 1993, 1994 International Business Machines Corp.-->
<!-- (c) Copyright 1993, 1994 Sun Microsystems, Inc.-->
<!-- (c) Copyright 1993, 1994 Novell, Inc.-->
<RefSynopsisDiv>
<CmdSynopsis>
<Command>ttsnoop</Command>
<Arg Choice="opt">&minus;t</Arg>
</CmdSynopsis>
</RefSynopsisDiv>
<RefSect1>
<Title>DESCRIPTION</Title>
<Para>Then
<Command>ttsnoop</Command> utility allows
its user to create and send custom constructed ToolTalk messages, and to
selectively monitor any or all ToolTalk messages on your system.
<command>ttsnoop</command> menu options are as follows:
</para>
<itemizedlist>
<listitem>
<para>Snoop &mdash; Turn on/off tracing; get version information
</para>
</listitem>
<listitem>
<para>Message &mdash; Create, open, receive, and destroy messages
</para>
</listitem>
<listitem>
<para>Pattern &mdash; Create, open, and destroy patterns
</para>
</listitem>
<listitem>
<para>File &mdash; Numerous tasks, including joining a file
</para>
</listitem>
<listitem>
<para>Session &mdash; Join a specific session; set the default session
</para>
</listitem>
<listitem>
<para>Ptype &mdash; Declare and undeclare a <literal>ptype</literal>; determine whether
a <literal>ptype</literal> exists
</para>
</listitem>
<listitem>
<para>Types &mdash; Generate a list of declared types; generate a list of ToolTalk-based actions
</para>
</listitem>
<listitem>
<para>Procid &mdash; Open, close, suspend, and resume a procid
</para>
</listitem>
<listitem>
<para>libc &mdash; Call <function>system()</function>, <function>putenv()</function>, <function>chdir()</function>, <function>pause()</function>, and <function>exit()</function>; use <function>exit()</function>
to exit <command>ttsnoop</command>
</para>
</listitem>
</itemizedlist>
</RefSect1>
<RefSect1>
<Title>OPTIONS</Title>
<Para>The following command-line options are available:
</Para>
<VariableList>
<VarListEntry>
<Term><Literal>&minus;t</Literal></Term>
<ListItem>
<Para>Print trace output. Of particular interest is that ttsnoop
will print example ToolTalk API code in the invoking OpenWindows
cmdtool (or console if ttsnoop is invoked via a menu choice)
showing what ToolTalk API calls are being used to construct
a particular pattern or message.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>SEE ALSO</Title>
<Para>&cdeman.ttsession;</Para>
</RefSect1>
</RefEntry>
<!--fickle 1.12 mancsf-to-docbook 1.3 08/21/95 21:30:04-->