event is a shared event client and server. Events are stored in a persistent database named by the
name operand. Each
event has a name, an expiration, and a binary status
raised or
not-raised. A non-existent event is
not-raised.
Events may be raised, deleted, cleared, tested and waited for. If no
request operands are specified then requests are
prompted for, with an
EVENT> prompt, and read from the standard input. Multiple command line requests must be separated
by
:. In the following events operands are matched by
ksh(1) patterns.
The client requests are:
- all connection
Raise all pending events for the connection. Mainly for
debugging.
- clear event ...
Mark event not-raised but do not delete from the
database. This allows the events to be matched by patterns.
- delete event ...
Delete event.
- exit
- Close the client connection.
- hold [ event ...]
If event operands are specified then clients are not
notified about the those events until they are explicitly released by release event ... If no events are specified
then all current and future events will be unconditionally held until a release with no event operands.
- info
- List the server status pending events by client connection. The list is terminated by a done
message.
- list [ pattern ]
Start an event dictionary scan and list the first event. If pattern
is specified then only events matching pattern are listed.
- next
- List the next event in the list event scan. The list is terminated by a done
message.
- quit
- Equivalent to exit.
- raise event ...
Raise event ...
- release [ event ...]
If event operands are specified then they are
released from a previous hold event ... If no event operands are specified then any previous unconditional hold
is turned off.
- set option ...
- stop
- Terminate the server. Persistent data is preserved.
- test event
Determine the event status.
- wait event
Wait for event status to be raised.
The
--cs,
--expire,
--initialize, and
--log options apply to the initial service command, and the
--expire
,
--log,
--newer,
--older, and
--quiet options apply to client requests.