HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

evm.auth(4) evm.auth(4)

The keywords described may be entered in a case-insensitive manner. The allowable strings and the

minimum number of characters is shown in the following table. A minimum of zero (

0) indicates that all

characters are required.

Keyword Minimum

access 0

class 0

event_rights 7

execute 4

post 0

service 4

service_rights 9

Notes

1. If you add an

event_rights entry to the authorization ﬁle, you must make sure there is a

corresponding base event template in the template ﬁle library. The base template must have a name

whose components exactly match the corresponding components in the authorization ﬁle’s

class value.

The template name can have fewer components than are present in the

class, but it cannot have

more. For example, if an

event_rights group has a class value of myco.myprod.payroll

and an event template with the name

myco.myprod has been registered in an EVM template ﬁle, the

template will be regarded as the base template for the class.

Each time the daemon loads or reloads its conﬁguration, it writes a warning message in its error ﬁle if

no base template is registered for a particular event_rights entry. Refer to the evmtemplate(4)

manpage for information about registering event templates.

2. If you are concerned with allowing your ﬁle to be used on other systems that support EVM in the future,

you should use the built-in macro @SYS_VP@ in place of the ﬁrst two components (

sys.unix) of the

name of any system event. This will make it unnecessary to change the ﬁle if the other system uses a

different event name preﬁx.

EXAMPLES

This example illustrates an entry in the authorization ﬁle with the following privileges: Only root may post

events that have

myco.myapp as the ﬁrst two components of the event name.

Events in this class may be accessed by root or by any user who is a member of the tech group.

event_rights {

class myco.myapp

post +root

access "+root, +group=tech"

}

FILES

/etc/evm.auth Location of the EVM authorization ﬁle.