Initial import of the CDE 2.1.30 sources from the Open Group.

This commit is contained in:
Peter Howkins
2012-03-10 18:21:40 +00:00
commit 83b6996daa
18978 changed files with 3945623 additions and 0 deletions

View File

@@ -0,0 +1,263 @@
<!-- $XConsortium: dtspcd.sgm /main/7 1996/09/23 14:38:34 cdedoc $ -->
<!-- (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.MAN39.rsml.1">
<RefMeta>
<RefEntryTitle>dtspcd</RefEntryTitle>
<ManVolNum>user cmd</ManVolNum>
</RefMeta>
<RefNameDiv>
<RefName><Command>dtspcd</Command></RefName>
<RefPurpose>CDE Subprocess Control Service
</RefPurpose>
</RefNameDiv>
<!-- CDE Common Source Format, Version 1.0.0-->
<!-- *************************************************************************-->
<!-- ** (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>dtspcd</Command>
<Arg Choice="opt">&minus;debug</Arg>
<Arg Choice="opt">&minus;log</Arg>
<Arg Choice="opt">&minus;auth_dir<Replaceable>directory</Replaceable></Arg>
<Arg Choice="opt">&minus;timeout<Replaceable>num_minutes</Replaceable></Arg>
<Arg Choice="opt">&minus;mount_point<Replaceable>mount_point</Replaceable></Arg>
</CmdSynopsis>
</RefSynopsisDiv>
<RefSect1>
<Title>DESCRIPTION</Title>
<Para>The daemon for the
CDE Subprocess Control service,
<Command>dtspcd</Command>, is not intended to be started directly by the user,
rather it should be started automatically by the inetd
daemon (see
<filename moreinfo="RefEntry">inetd</filename>(1m)) in response to a CDE client
requesting a process to be started on the daemon's host.
</Para>
</RefSect1>
<RefSect1>
<Title>OPTIONS</Title>
<VariableList>
<VarListEntry>
<Term><Literal>&minus;auth_dir</Literal> <Emphasis>directory</Emphasis></Term>
<ListItem>
<Para>The default authentication directory is the user's
$HOME directory.
This option allows the system
administrator to use a different directory.
Note that
<Emphasis>directory</Emphasis> must be exported to hosts wishing
to use the
<Literal>dtspc</Literal> service.
<Emphasis>directory</Emphasis> &minus; the name of the directory to use for authentication.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Literal>&minus;timeout</Literal> <Emphasis>minutes</Emphasis></Term>
<ListItem>
<Para>By default, the dtspcd process will terminate if it does
not have any activity (process start or process stop)
for 10 minutes and
<Command>dtspcd</Command> has no child processes running.
To change the timeout, set
<Emphasis>minutes</Emphasis> to the
desired number of minutes.
To force the daemon to not use a timer,
set
<Emphasis>minutes</Emphasis> to &minus;1.
<Emphasis>minutes</Emphasis> &minus; the number of minutes for the timer.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Literal>&minus;mount_point</Literal> <Emphasis>mount_point</Emphasis></Term>
<ListItem>
<Para>The file system's mount point is named
<Emphasis>mount_point.</Emphasis> For example,
<Emphasis>mount_point</Emphasis> could
be "/net" or "/nfs".
The daemon sets the
environment variable
<Emphasis>DTMOUNTPOINT</Emphasis> to the
value of
<Emphasis>mount_point</Emphasis>. This value
of
<Emphasis>DTMOUNTPOINT</Emphasis> will override all other
definitions of
<Emphasis>DTMOUNTPOINT</Emphasis>.</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Literal>&minus;log</Literal></Term>
<ListItem>
<Para>This option turns on logging of status information
to the file
<Filename>/var/dt/tmp/DTSPCD.log</Filename>. The information logged
includes the name of the client host, the client's
username, error messages and the name of the file
used for authentication.
The default is to not do any logging.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Literal>&minus;debug</Literal></Term>
<ListItem>
<Para>This option turns on logging of dtspc protocol
to the file
<Filename>/var/dt/tmp/DTSPCD.log.</Filename> The
protocol information logged includes
the name of the protocol and number of bytes
in the request.
The default is to not log the protocol.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>AUTHENTICATION</Title>
<Para>When a CDE client attempts to connect to a
<Command>dtspcd</Command> daemon,
the client sends the daemon its username.
The
daemon uses the username to determine the user's
home directory on the daemon's host.
The home
directory is used during authentication and it
must be readable by the daemon and writable by
the client.
Therefore, the user's home directory
on the daemon's host must be mounted to the client
host.
If the user's home directory is not readable
and the
<Literal>&minus;auth_dir</Literal> command line option is not used,
the directory
<Filename>/var/dt/tmp</Filename> will be used.
</Para>
<Para>To use a directory other than the user's home directory
for authentication, use the
<Literal>&minus;auth_dir</Literal> command
line option.
</Para>
</RefSect1>
<RefSect1>
<Title>CONFIGURATION</Title>
<Para>The
<Command>dtspcd</Command> daemon is an Internet service that must
be registered in the file
<Filename>/etc/services</Filename> as follows:
</Para>
<ProgramListing>dtspc 6112/tcp
</ProgramListing>
<Para>and in the file
<Filename>/etc/inetd.conf</Filename> as follows:
</Para>
<ProgramListing>dtspc stream tcp nowait root /usr/dt/bin/dtspcd /usr/dt/bin/dtspcd
</ProgramListing>
</RefSect1>
<RefSect1>
<Title>ENVIRONMENT VARIABLE MANAGEMENT</Title>
<Para>The CDE Subprocess Control service allows
the user and system administrator to
create files of environment variable
definitions to be placed in the
processes environment before a remote
process is started.
See &cdeman.dtspcdenv; for more information.
</Para>
</RefSect1>
<RefSect1>
<Title>OPERATING SYSTEM DEPENDENCIES</Title>
<Para>On HP-UX, the file
<Filename>/usr/adm/inetd.sec</Filename> may be used to
control access to the
<Command>dtspcd</Command> daemon.
See
<Filename MoreInfo="RefEntry">inetd.sec</Filename>(4) for more information.
</Para>
</RefSect1>
<RefSect1>
<Title>FILES</Title>
<VariableList>
<VarListEntry>
<Term><Filename>/usr/dt/bin/dtspcd</Filename></Term>
<ListItem>
<Para>The CDE Subprocess Control daemon
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Filename>/etc/services</Filename></Term>
<ListItem>
<Para>The Internet service name data base
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Filename>/etc/inted.conf</Filename></Term>
<ListItem>
<Para>The inetd configuration file
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Filename>/etc/dt/config/dtspcdenv</Filename></Term>
<ListItem>
<Para>System-wide, locally defined environment variable
definitions used when a process is executed
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Filename>/usr/dt/config/dtspcdenv</Filename></Term>
<ListItem>
<Para>System-wide, installed environment variable definitions
used when a process is executed
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Filename>$HOME/.dt/dtspcdenv</Filename></Term>
<ListItem>
<Para>User-specific environment variable definitions used
when a process is executed
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term><Filename>/var/dt/tmp/DTSPCD.log</Filename></Term>
<ListItem>
<Para>The dtspcd log file
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>DIAGNOSTICS</Title>
<Para>Use the command line options
<Literal>&minus;log</Literal> and
<Literal>&minus;debug</Literal> (described above) to get diagnostic
information.
</Para>
</RefSect1>
<RefSect1>
<Title>SEE ALSO</Title>
<Para><filename moreinfo="RefEntry">inetd</filename>(1m), <Filename MoreInfo="RefEntry">services</Filename>(4), <Filename MoreInfo="RefEntry">inetd.conf</Filename>(4), &cdeman.dtspcdenv;.
</Para>
</RefSect1>
</RefEntry>
<!--fickle 1.12 mancsf-to-docbook 1.2 08/07/95 23:05:27-->

View File

@@ -0,0 +1,190 @@
<!-- $XConsortium: rpccmsd.sgm /main/7 1996/10/30 16:33:29 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.MAN40.rsml.1" Remap="">
<RefMeta>
<RefEntryTitle>rpc.cmsd</RefEntryTitle>
<ManVolNum>user cmd</ManVolNum>
</RefMeta>
<RefNameDiv>
<RefName><Command>rpc.cmsd</Command></RefName>
<RefPurpose>calendar manager service daemon
</RefPurpose>
</RefNameDiv>
<!--.IP "&bsol;&bsol;$1" &bsol;" ex-TP
-->
<!-- CDE Common Source Format, Version 1.0.0-->
<!-- (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>rpc.cmsd
[&minus;d]</Command>
<Arg Choice="opt">&minus;s</Arg>
</CmdSynopsis>
</RefSynopsisDiv>
<RefSect1>
<Title>DESCRIPTION</Title>
<Para>The
<Command>rpc.cmsd</Command> is a small database manager for appointment and
resource-scheduling data. Its primary client is
<Command>dtcm</Command> a productivity tool included with CDE.
<Command>rpc.cmsd</Command> is normally invoked by <Filename moreinfo="RefEntry">inetd</filename>(1m) when a
<Command>dtcm</Command> request is received.
</Para>
</RefSect1>
<RefSect1>
<Title>OPTIONS</Title>
<Para>The following options are available:
</Para>
<VariableList>
<VarListEntry>
<Term>&minus;d</Term>
<ListItem>
<Para>Enables debugging output.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;s</Term>
<ListItem>
<Para>Runs rpc.cmsd in the foreground. This option should
be used when rpc.cmsd is invoked manually for debugging purposes.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>OPERANDS</Title>
<Para>None.
</Para>
</RefSect1>
<RefSect1>
<Title>STDIN</Title>
<Para>Not used.
</Para>
</RefSect1>
<RefSect1>
<Title>INPUT FILES</Title>
<Para>The database format used by the
<Command>rpc.cmsd</Command> is private.
</Para>
</RefSect1>
<RefSect1>
<Title>ENVIRONMENT VARIABLES</Title>
<Para>None.
</Para>
</RefSect1>
<RefSect1>
<Title>RESOURCES</Title>
<Para>None.
</Para>
</RefSect1>
<RefSect1>
<Title>ASYNCHRONOUS EVENTS</Title>
<Para>None.
</Para>
</RefSect1>
<RefSect1>
<Title>STDOUT</Title>
<Para>When the
<Literal>&minus;d</Literal> option is used,
<Command>rpc.cmsd</Command> writes the debugging information to stdout.
</Para>
</RefSect1>
<RefSect1>
<Title>STDOUT</Title>
<Para>None.
</Para>
</RefSect1>
<RefSect1>
<Title>OUTPUT FILES</Title>
<Para>None.
</Para>
</RefSect1>
<RefSect1>
<Title>EXTENDED DESCRIPTION</Title>
<Para>None.
</Para>
</RefSect1>
<RefSect1>
<Title>EXIT STATUS</Title>
<Para>When the process exits,
<Command>rpc.cmsd</Command> exits with the status of the exited child.
Otherwise, the following exit values are returned:
</Para>
<VariableList>
<VarListEntry>
<Term>0</Term>
<ListItem>
<Para>Normal termination.
A zero exit status means
<Command>rpc.cmsd</Command> has received a HUP signal, and terminated normally.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>-1</Term>
<ListItem>
<Para>Abnormal termination. Permissions on the database file or
directory were incorrect.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>1</Term>
<ListItem>
<Para>RPC memory management errors have prevented successful operation,
a socket operation failed in a nonrecoverable way, or could not create
a udp service.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>2</Term>
<ListItem>
<Para>Could not create a TLI connection.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>3</Term>
<ListItem>
<Para>Could not register the service.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>CONSEQUENCES OF ERRORS</Title>
<Para>The
<Command>rpc.cmsd</Command> utility takes the standard action for all signals.
</Para>
</RefSect1>
<RefSect1>
<Title>APPLICATION USAGE</Title>
<Para>To run
<Command>rpc.cmsd</Command> in standalone mode, the user must be root.
</Para>
</RefSect1>
<RefSect1>
<Title>EXAMPLES</Title>
<Para>None.
</Para>
</RefSect1>
<RefSect1>
<Title>SEE ALSO</Title>
<Para>&cdeman.dtcm;, &cdeman.dtcm.lookup;, &cdeman.dtcm.delete;, &cdeman.dtcm.insert;, <filename moreinfo="RefEntry">inetd</filename>(1m).</Para>
</RefSect1>
</RefEntry>
<!--fickle 1.12 mancsf-to-docbook 1.2 08/07/95 01:31:55-->

View File

@@ -0,0 +1,131 @@
<!-- $XConsortium: rpcttdbs.sgm /main/6 1996/09/08 20:22:30 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.MAN41.rsml.1" Remap="">
<RefMeta>
<RefEntryTitle>ttdbserver</RefEntryTitle>
<ManVolNum>user cmd</ManVolNum>
</RefMeta>
<RefNameDiv>
<RefName><Command>ttdbserver</Command></RefName>
<RefPurpose>RPC-based ToolTalk database server
</RefPurpose>
</RefNameDiv>
<!-- $XConsortium: rpcttdbs.sgm /main/6 1996/09/08 20:22:30 rws $-->
<!-- (c) Copyright 1993, 1994 Sun Microsystems, Inc.-->
<!-- (c) Copyright 1993, 1994 Hewlett-Packard Company-->
<!-- (c) Copyright 1993, 1994 International Business Machines Corp.-->
<RefSynopsisDiv>
<CmdSynopsis>
<Command>rpc.ttdbserver</Command>
<Arg Choice="opt">-G</Arg>
<Arg Choice="opt">-m DTMOUNTPOINT_value</Arg>
<Arg Choice="opt">-n</Arg>
<!--.RB [ -t \ level]-->
<Arg Choice="opt">-v</Arg>
<Arg Choice="opt">-?</Arg>
<!-- This was disabled for release 1.0-->
<!-- [-a authentication-level]-->
</CmdSynopsis>
</RefSynopsisDiv>
<RefSect1>
<Title>DESCRIPTION</Title>
<Para><Command>rpc.ttdbserver</Command> is the ToolTalk database server daemon. This process (normally
started by
<Literal>inetd</Literal>) performs all database operations for databases
stored on the host.
</Para>
</RefSect1>
<RefSect1>
<Title>OPTIONS</Title>
<VariableList>
<VarListEntry>
<Term>&minus;G</Term>
<ListItem>
<!-- ex-TP-->
<Para>Perform garbage collection.
This cleans up the TT_DB directories and the associated internal
database files.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;m DTMOUNTPOINT_value</Term>
<ListItem>
<!-- ex-TP-->
<Para>Sets the DTMOUNTPOINT environment variable for
<Literal>rpc.ttdbserver.</Literal> If there is already an environment variable called DTMOUNTPOINT, -m
will override it.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;n</Term>
<ListItem>
<!-- ex-TP-->
<Para>Turn off permission checking. Normally the protection of the file
containing the spec determines who may read and write that spec. This
option disables this checking and allows anyone to read and write any
spec. This option should be used with caution.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;v</Term>
<ListItem>
<!-- ex-TP-->
<Para>Print out the version number.
<!--.TP--><!--.B \-t level--><!--Turns on trace level, the valid level is between 1 to 10.--></Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;?</Term>
<ListItem>
<!-- ex-TP-->
<Para>Prints out the command usage information.
<!-- .TP--><!-- .B \-a authentication-level--><!-- Set the authentication level to either--><!-- .I unix--><!-- (the default), or to--><!-- .I des--><!-- which means to use secure RPC.--></Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>ENVIRONMENT</Title>
<VariableList>
<VarListEntry>
<Term>DTMOUNTPOINT</Term>
<ListItem>
<!-- ex-TP-->
<Para>If set, the value of this environment variable will be used in place
of "/net" in pathnames constructed for the automounters host map.
This environment variable can also be set by using the -m flag for
<Literal>rpc.ttdbserver.</Literal></Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>FILES</Title>
<VariableList>
<VarListEntry>
<Term>TT_DB/*</Term>
<ListItem>
<!-- ex-TP-->
<Para>The NetISAM database files are kept in the TT_DB directory under each
disk partition mount point.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>SEE</Title>
<Para>&cdeman.ttsession; &cdeman.tt.file.netfile;</Para>
</RefSect1>
</RefEntry>
<!--fickle 1.12 mancsf-to-docbook 1.2 08/07/95 01:31:55-->

View File

@@ -0,0 +1,276 @@
<!-- $XConsortium: ttdbck.sgm /main/5 1996/09/08 20:22:38 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.MAN44.rsml.1" Remap="">
<RefMeta>
<RefEntryTitle>ttdbck</RefEntryTitle>
<ManVolNum>user cmd</ManVolNum>
</RefMeta>
<RefNameDiv>
<RefName><Command>ttdbck</Command></RefName>
<RefPurpose>display, check, or repair ToolTalk databases
</RefPurpose>
</RefNameDiv>
<!-- $XConsortium: ttdbck.sgm /main/5 1996/09/08 20:22:38 rws $-->
<!-- (c) Copyright 1993, 1994 Sun Microsystems, Inc.-->
<!-- (c) Copyright 1993, 1994 Hewlett-Packard Company-->
<!-- (c) Copyright 1993, 1994 International Business Machines Corp.-->
<RefSynopsisDiv>
<CmdSynopsis>
<Command>ttdbck</Command>
<Arg Choice="opt"><Replaceable>selection opts</Replaceable></Arg>
<Arg Choice="opt"><Replaceable>diagnosis opts</Replaceable></Arg>
<Arg Choice="opt"><Replaceable>display opts</Replaceable></Arg>
<Arg Choice="opt"><Replaceable>repair opts</Replaceable></Arg>
<Arg Choice="opt"><Replaceable>data-base-directory</Replaceable></Arg>
<Arg>...</Arg>
</CmdSynopsis>
</RefSynopsisDiv>
<RefSect1>
<Title>DESCRIPTION</Title>
<Para><Command>ttdbck</Command> is the ToolTalk database maintenance tool.
It allows direct inspection of ToolTalk spec data, detection of
inconsistencies, and repair of problems.
</Para>
</RefSect1>
<RefSect1>
<Title>OPTIONS</Title>
<VariableList>
<VarListEntry>
<Term>data-base-directory</Term>
<ListItem>
<!-- ex-TP-->
<Para>Names the directory or directories containing the ToolTalk database to be
inspected or repaired. If no directories are named, the current directory is
assumed. If a directory path does not end in ``TT_DB'', ``TT_DB''
is appended.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term></Term>
<ListItem>
<Para>The user running the command must have read access to the files in the
directory to inspect the data and write access to repair the data.
Since ToolTalk databases are typically accessible only to root, this
command is normally run as root.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
<RefSect2>
<Title>Selection options</Title>
<Para>The selection options determine which specs in the database are displayed
or modified. If no selection options are given, all specs in the database
are displayed. To prevent massive accidental changes to ToolTalk
databases, no repair options except
<Option>-I</Option> are allowed unless a selection or
diagnosis option is given.
</Para>
<VariableList>
<VarListEntry>
<Term>&minus;f&ensp; filename</Term>
<ListItem>
<!-- ex-TP-->
<Para>Restricts the set of specs to be inspected or modified to those which
describe objects in the named file. The file name can contain shell-style
wildcards which must be escaped to prevent the shell from expanding them.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;k&ensp; objidkey</Term>
<ListItem>
<!-- ex-TP-->
<Para>An object id key, specifying a particular spec to be displayed or modified.
The object id key can be obtained from a previous invocation of
<Command>ttdbck</Command>; one might display a set of specs, determine the one that needs repair, and
specify its key here.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;t&ensp; type</Term>
<ListItem>
<!-- ex-TP-->
<Para>Restricts the set of specs to be inspected or modified to those with
otype
<Emphasis>type.</Emphasis> The type name can contain shell-style wildcards which must be escaped
to prevent the shell from expanding them.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Diagnosis options</Title>
<Para>These options check for and report on inconsistencies in the selected specs.
Only specs selected by the selection options are checked. If a diagnosis
option is given, any display or repair option is applied only to specs which
fail the diagnostic check.
</Para>
<VariableList>
<VarListEntry>
<Term>&minus;b</Term>
<ListItem>
<!-- ex-TP-->
<Para>Check for badly formed specs: those which have no file or type or those
which have types not defined in the type database.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;x</Term>
<ListItem>
<!-- ex-TP-->
<Para>Check for specs which refer to files that no longer exist.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Display options</Title>
<Para>These options determine which data is printed for each selected spec.
</Para>
<VariableList>
<VarListEntry>
<Term>&minus;i</Term>
<ListItem>
<!-- ex-TP-->
<Para>Display the object id (including the object id key.)
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;m</Term>
<ListItem>
<!-- ex-TP-->
<Para>Display the mandatory data that must appear in every spec: the otype
of the object described by the spec and the file in which the spec is
stored.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;p</Term>
<ListItem>
<!-- ex-TP-->
<Para>Display all the properties and values for each selected spec.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;a</Term>
<ListItem>
<!-- ex-TP-->
<Para>Display all data (equivalent to specifying
<Literal>&minus;imp</Literal>)</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Repair options</Title>
<VariableList>
<VarListEntry>
<Term>&minus;I</Term>
<ListItem>
<!-- ex-TP-->
<Para>Invoke the NetISAM isrepair() function for all files accessed.
This action is applied before any other inspection or repair
action.
This option should be used when normal operations
return EBADFILE (error code 105).
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;F &ensp;filename</Term>
<ListItem>
<!-- ex-TP-->
<Para>Change the file name for the selected specs to the supplied file name.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;T &ensp;otypeid</Term>
<ListItem>
<!-- ex-TP-->
<Para>Change the type of the selected specs to the given otype.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;Z</Term>
<ListItem>
<!-- ex-TP-->
<Para>Remove the selected specs entirely.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
</RefSect1>
<RefSect1>
<Title>EXAMPLES</Title>
<VariableList>
<VarListEntry>
<Term></Term>
<ListItem>
<Para><Command>ttdbck</Command> <Literal>-bxi</Literal> <Filename>/home</Filename></Para>
<Para>In the /home/TT_DB directory, finds all badly formed specs and specs that
refer to non-existent files and prints their ids.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term></Term>
<ListItem>
<Para><Command>ttdbck</Command> <Literal>-f</Literal> <Filename>/home/sample/data</Filename> <Literal>-F</Literal> <Filename>/home/sample/data1</Filename> <Filename>/home</Filename></Para>
<Para>In the /home/TT_DB directory, finds all specs that refer to objects in
file /home/sample/data and changes them to refer to /home/sample/data1.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term></Term>
<ListItem>
<Para><Command>ttdbck</Command> <Option>-t</Option> <Literal>Sample_Otype_Name</Literal> <Literal>-Z</Literal> <Filename>/export/TT_DB</Filename></Para>
<Para>In the /export/TT_DB directory, finds all specs that refer to objects
of type
<Emphasis>Sample_Otype_Name</Emphasis> and deletes the specs.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>FILES</Title>
<VariableList>
<VarListEntry>
<Term>/path/TT_DB</Term>
<ListItem>
<!-- ex-TP-->
<Para>ToolTalk database
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>NOTES</Title>
<Para>The
<Command>ttdbck</Command> command should be run on the same machine where the TT_DB files
being inspected and repaired physically exist. That is, don't try to access
the TT_DB files via NFS.
</Para>
</RefSect1>
</RefEntry>
<!--fickle 1.12 mancsf-to-docbook 1.2 08/07/95 01:31:55-->

View File

@@ -0,0 +1,219 @@
<!-- $XConsortium: ttdbserv.sgm /main/7 1996/12/06 18:09:14 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.MAN45.rsml.1" Remap="">
<RefMeta>
<RefEntryTitle>ttdbserverd</RefEntryTitle>
<ManVolNum>user cmd</ManVolNum>
</RefMeta>
<RefNameDiv>
<RefName><Command>ttdbserverd</Command></RefName>
<RefPurpose>RPC-based ToolTalk database server
</RefPurpose>
</RefNameDiv>
<!-- (c) Copyright 1993, 1994 Sun Microsystems, Inc.-->
<!-- (c) Copyright 1993, 1994 Hewlett-Packard Company-->
<!-- (c) Copyright 1993, 1994 International Business Machines Corp.-->
<RefSynopsisDiv>
<CmdSynopsis>
<Command>rpc.ttdbserverd</Command>
<Arg Choice="opt">&minus;G</Arg>
<Arg Choice="opt">&minus;m <Replaceable>DTMOUNTPOINT_value</Replaceable></Arg>
<Arg Choice="opt">&minus;n</Arg>
<!--.RB [ -t \ level]-->
<Arg Choice="opt">&minus;v</Arg>
<Arg Choice="opt">&minus;?</Arg>
<!-- This was disabled for release 1.0-->
<!-- [-a authentication-level]-->
</CmdSynopsis>
</RefSynopsisDiv>
<RefSect1>
<Title>DESCRIPTION</Title>
<Para><Command>rpc.ttdbserverd</Command>
manages ToolTalk objects created by
&cdeman.tt.spec.create;,
and handles certain queries related to the netfiles returned by
&cdeman.tt.file.netfile;.
One instance of
<Command>rpc.ttdbserverd</Command>
(normally started by
<Command>inetd</Command>)
runs on each host that has a local filesystem.
<Command>rpc.ttdbserverd</Command>
serves four purposes:</Para>
<OrderedList>
<ListItem>
<Para>Mapping a spec to its associated file and a file to its associated specs.
</Para>
</ListItem>
<ListItem>
<Para>Mapping a spec to its properties.
</Para>
</ListItem>
<ListItem>
<Para>Mapping a file to a list of sessions with clients having patterns
registered in the scope of that file.
</Para>
</ListItem>
<ListItem>
<Para>Answering netfile queries; see
&cdeman.tt.file.netfile;
and
&cdeman.tt.host.file.netfile;.
</Para>
</ListItem>
</OrderedList>
<Para>For each filesystem that
<Command>rpc.ttdbserverd</Command>
needs to store information about, it creates a directory called
<Filename>TT_DB</Filename> at the mountpoint of that file system.
In that directory
it creates the databases it needs to store its tables and indices.
If the partition is not writable, then
<Command>rpc.ttdbserverd</Command>
can be told, via
<Filename MoreInfo=RefEntry>partition_map</Filename>(4),
to create the databases in another local partition.
If
<Command>rpc.ttdbserverd</Command>
is not installed on a particular file server, ToolTalk can be
told, via
<Filename MoreInfo=RefEntry>hostname_map</Filename>(4),
to manage that file server's partitions using the
<Command>rpc.ttdbserverd</Command>
on a different host.
</Para>
</RefSect1>
<RefSect1>
<Title>OPTIONS</Title>
<VariableList>
<VarListEntry>
<Term>&minus;G</Term>
<ListItem>
<Para>Perform garbage collection.
This cleans up the <Filename>TT_DB</Filename> directories and the
associated internal database files.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;m <Replaceable>DTMOUNTPOINT_value</Replaceable></Term>
<ListItem>
<Para>Sets the <SystemItem Class="EnvironVar">DTMOUNTPOINT</SystemItem>
environment variable for
<Command>rpc.ttdbserverd</Command>.
If there is already an environment variable called
<SystemItem Class="EnvironVar">DTMOUNTPOINT</SystemItem>, &minus;m
will override it.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;n</Term>
<ListItem>
<Para>Turn off permission checking. Normally the protection of the file
passed to
&cdeman.tt.spec.create;
determines who may read and write that spec. This
option disables this checking and allows anyone to read and write any
spec. This option should be used with caution.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>&minus;v</Term>
<ListItem>
<Para>Print out the version number.
</Para>
</ListItem>
</VarListEntry>
<!--.TP-->
<!--.B \-t level-->
<!--Turns on trace level, the valid level is between 1 to 10.-->
<VarListEntry>
<Term>&minus;?</Term>
<ListItem>
<Para>Prints out the command usage information.
</Para>
</ListItem>
</VarListEntry>
<!-- .TP-->
<!-- .B \-a authentication-level-->
<!-- Set the authentication level to either-->
<!-- .I unix-->
<!-- (the default), or to-->
<!-- .I des-->
<!-- which means to use secure RPC.-->
</VariableList>
</RefSect1>
<RefSect1>
<Title>ENVIRONMENT</Title>
<VariableList>
<VarListEntry>
<Term>DTMOUNTPOINT</Term>
<ListItem>
<Para>If set, the value of this environment variable will be used in place
of <Filename>/net</Filename> in pathnames constructed to answer
&cdeman.tt.host.netfile.file;
queries. This environment variable can also be set by using the &minus;m
flag for <Command>rpc.ttdbserverd</Command>.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>TT_PARTITION_MAP</Term>
<ListItem>
<Para>If set, the value of this environment variable will be used
in place of <Filename>/etc/tt/partition_map</Filename>. See
<Filename MoreInfo=RefEntry>partition_map</Filename>(4).
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>FILES</Title>
<VariableList>
<VarListEntry>
<Term>TT_DB/*</Term>
<ListItem>
<Para>spec and session database files are kept in the TT_DB directory
under each disk partition mount point.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>tt/hostname_map</Term>
<ListItem>
<Para>Host redirection map. See
<Filename MoreInfo=RefEntry>hostname_map</Filename>(4).
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>/etc/tt/partition_map</Term>
<ListItem>
<Para>Partition redirection map. See
<Filename MoreInfo=RefEntry>partition_map</Filename>(4).
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect1>
<RefSect1>
<Title>SEE ALSO</Title>
<Para>&cdeman.ttsession;,
&cdeman.tt.file.netfile;,
&cdeman.tt.host.file.netfile;,
&cdeman.tt.spec.create;,
<Filename MoreInfo=RefEntry>hostname_map</Filename>(4),
<Filename MoreInfo=RefEntry>partition_map</Filename>(4)
</Para>
</RefSect1>
</RefEntry>