event - shared event client and server


event [ options ] name [ request [ options ] [ arg ... ] ] [ : request ... ]


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.
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.
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.
List the next event in the list event scan. The list is terminated by a done message.
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 ...
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.


-c, --cs|connect-stream=connect-stream

Use connect-stream instead of the default. The default value is /dev/tcp/local/event.
-e, --expire=date-expression

Set the current event expiration to the date(1) or cron(1) expression date-expression.
-i, --initialize

Initialize the service if it is not already running.
-l, --log

Log server activity to state-name.log, where state-name is the state path name sans suffix. On by default; -l means --nolog.
-n, --newer=date

Match events newer than date. If --older is also specified then only event times > newer and < older match.
-o, --older=date

Match events older than date. If --newer is also specified then only event times > newer and < older match.
-q, --quiet

Suppress request confirmation messages.


Expirations, logging and the set request are not implemented yet.


coshell(1), cs(1), nmake(1), dbm(3), ndbm(3), gdbm(3)



event (AT&T Research) 2007-06-05

Glenn Fowler <glenn.s.fowler@gmail.com>

Copyright © 1990-2012 AT&T Intellectual Property