xref: /illumos-gate/usr/src/cmd/syseventd/etc/README (revision bbf21555)
1#
2# CDDL HEADER START
3#
4# The contents of this file are subject to the terms of the
5# Common Development and Distribution License, Version 1.0 only
6# (the "License").  You may not use this file except in compliance
7# with the License.
8#
9# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
10# or http://www.opensolaris.org/os/licensing.
11# See the License for the specific language governing permissions
12# and limitations under the License.
13#
14# When distributing Covered Code, include this CDDL HEADER in each
15# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
16# If applicable, add the following below this CDDL HEADER, with the
17# fields enclosed by brackets "[]" replaced with your own identifying
18# information: Portions Copyright [yyyy] [name of copyright owner]
19#
20# CDDL HEADER END
21#
22#
23
24#
25# Copyright (c) 2001 by Sun Microsystems, Inc.
26# All rights reserved.
27#
28
29Configuration files for syseventd(8).
30
31These files are not intended to be edited and any changes made
32will not be preserved across upgrades.
33
34The format for file names in this directory is:
35
36	<vendor>,[<publisher>,][<class>,[<subclass>,]]sysevent.conf
37
38Files with a suffix other than ',sysevent.conf' are ignored.
39
40After making a change to a file in this directory, restart the
41syseventd daemon by issuing:
42
43	pkill -HUP syseventd
44
45
46The format for each line in a sysevent.conf file is:
47
48	<class> <subclass> <vendor> <publisher> <user> <reserved1>
49		<reserved2> <path> <arguments>
50
51<class>, <subclass>, <vendor> or <publisher> may be "-" to
52match any class, subclass, vendor or publisher, respectively.
53
54<user> may be "-" for commands to be invoked as root, or a
55valid user name.
56
57<reserved1> and <reserved2> must be "-".
58
59<path> must be the path of the command to be invoked in response
60to the event, and must be executable by <user>.
61
62<arguments> are optional, and may be any arbitrary arguments
63for the command to be invoked.  Macros may be used to substitute
64actual parameters from the matching event on the command line.
65