NOTIFICATION(5)
NAME
notification − CodeManager notification file
SYNOPSIS
Codemgr_wsdata/notification
DESCRIPTION
The notification file is edited by users to register notification requests. The notification facility permits CodeManager commands to detect CodeManager events that involve a workspace and to send electronic mail in response to the event. The following are the events that can be registered:
bringover-from
bringover-to
putback-from
putback-to
undo
workspace-delete
workspace-move
workspace-reparent
workspace-reparent-to
Whenever a user creates a workspace, a default notification file is created in the Codemgr_wsdata metadata directory. The default file consists of a large comment that describes the format of the file (the "#" character at the beginning of a line delimits a comment). Users update this file using a text editor; there is no special CodeManager command to do this.
The following is a copy of the default notification file. It describes the format of the file.
VERSION 1
#
# A workspace’s notification file.
#
# Note: Because this file is edited manually, you may
# want to maintain it using SCCS.
#
# The format for each entry is:
#
# email_address event ...
# BEGIN
# file1
# dir
# .
# .
# .
# END
#
# where <email_address> is the address to which the mail will be sent;
# <event> is one of the following:
# bringover-from
# bringover-to
# putback-from
# putback-to
# undo
# workspace-delete
# workspace-move
# workspace-reparent
# workspace-reparent-to
#
# The bringover, putback, and undo events can include a list of files and
# directories to be associated with the event. When a directory is listed,
# all files hierarchically beneath it are registered. The list must be
# delimited by BEGIN and END statements. To get registration for all files
# in the workspace, use a list of ".", an empty list, or no list.
#
# The following is a sample notification file:
#
# chip@mach1 bringover-to
# BEGIN
# dir/foo.cc
# dir/bar.cc
# END
# biff@mach2 bringover-to putback-to
# BEGIN
# .
# END
# biff@mach2 workspace-move
#
In the sample notification file above, the first entry causes mail to be sent to chip whenever a user brings over the files dir/foo.cc and dir/bar.cc into the workspace. The second entry causes mail to be sent to biff whenever a user brings over or puts back any files into the workspace. The third entry causes mail to be sent to biff when the workspace is moved.
SEE ALSO
CodeManager User’s Guide
bringover(1), def.dir.flp(1), filemerge(1), fileresolve(1), putback(1), resolve(1), ws_undo(1), workspace(1), access_control(5), args(5), children(5), conflicts(5), history(5), locks(5), nametable(5), notification(5), parent(5), putback.cmt(5)
SunOS 3.0.1 — Last change: 01 December 1992