[ новости /+++ | форум | теги | ]

NAME
     rpc.cmsd - calendar manager service daemon

SYNOPSIS
     rpc.cmsd [-c] [-d] [-g hhmm]

DESCRIPTION
     The rpc.cmsd is a small database  manager  for  appointment
     and resource-scheduling  data.  Its  primary client is dtcm,
     a  productivity  tool  included  with  CDE.  rpc.cmsd is
     normally  invoked by inetd(1M) when a rpc request is
     received.

     When rpc.cmsd is started, it reads its configuration file
     once.  It reads the configuration file again whenever it
     receives a SIGUSR1 signal.  Please refer to the manual page
     of cmsd.conf(4) for more information.

     By default, rpc.cmsd does garbage collection by writing the
     internal calendar image out to the calendar file at 4:00 am
     each day.  If the -g option is specified, rpc.cmsd does gar-
     bage collection at the specified time instead of the default
     time.

     The local super-user has special administrative privilege
     and has full access to all calendars residing on the local
     machine.

OPTIONS
     The following options are available:

        -c    Turns on strict CSA access mode.  In this mode,
              semi-private calendar entries (entries with the
              value of the classification attribute set to
              CSA_CLASS_CONFIDENTIAL (see csa(5)) are viewable
              only by users who are granted such view access.  By
              default, this mode is turned off and users who are
              not granted view access to semi-private calendar
              entries can see the time of such entries.

        -d    Enables debugging output.

        -g hhmm
              Specifies the time of garbage collection in the 24
              hour system.  hh is the hour number (0-23) and mm
              is the minute number (00-59).  The default is 0400.

OPERANDS
     None.

STDIN
     Not used.

INPUT FILES
     The database format used by the rpc.cmsd is private.

ENVIRONMENT VARIABLES
     None.

RESOURCES
     None.

ASYNCHRONOUS EVENTS
     Rpc.cmsd reacts to two signals.  If it receives the SIGHUP
     signal, it finishes processing the current rpc request and
     exits.  If it receives the SIGUSR1 signal, it finishes pro-
     cessing the current rpc request and rereads the configura-
     tion file.

STDOUT
     When the -d option is used, rpc.cmsd writes the debugging
     information to stdout.

STDERR
     None.

OUTPUT FILES
     None.

EXTENDED DESCRIPTION
     None.

EXIT STATUS
     When the process exits, rpc.cmsd exits with the status of
     the exited child.  Otherwise, the following exit values are
     returned:

        0   Normal termination.  A zero exit status means
            rpc.cmsd has received a SIGHUP signal, and terminated
            normally.

        -1  Abnormal termination.  Permissions on the database
            file or directory were incorrect.

        1   RPC memory managment errors have prevented successful
            operation, a socket operation failed in a nonrecover-
            able way, or could not create a udp service.

        2   Could not create a TLI connnection.

        3   Could not register the service.

CONSEQUENCES OF ERRORS
     The rpc.cmsd utility takes the standard action for all sig-
     nals.

APPLICATION USAGE
     To run rpc.cmsd in standalone mode, the user must be root.

EXAMPLES
     None.

SEE ALSO
     dtcm(1), dtcm_lookup(1), dtcm_delete(1), dtcm_insert(1),
     sdtcm_admin(1), sdtcm_convert(1), csa(5) inetd(1M)

Партнёры:

Хостинг: