...
If the file is detected, but does not complete before the inactive time elapses, the event occurrence will be set to a
rejected state. Since no event handler information is provided for a rejected occurrence, no further action will be taken by the UEM Server.
| Anchor |
|---|
| 104077410407761040774 |
|---|
| 1040776 |
|---|
|
If the UEM Server does not detect the presence of
uemtest.dat before the inactive time elapses, the event will be set to an
expired state. Again, because no handler information is given for this state, no further action will be taken by the UEM Server.
...
The command line options used in this example are:
Option | Description |
|---|
-host | List of one or more hosts upon which a command may run. |
-event_type | Type of event to monitor. |
-filespec | Name or pattern of the file whose creation should be detected and tracked for completion. |
-inact_date_time | Date and time at which the state of the monitored event should be made inactive. |
-userid | ID of a remote user account that the UEM Server uses to establish the security context in which event monitoring is performed. |
-pwd | Password associated with -userid. |
-triggered | Event state that, when encountered, will result in the execution of the associated event handler. |
-script | Complete path to a local script file that contains one or more system commands that should be executed on behalf of the event handler. |
-handler_opts | Options that are passed as command line arguments to any process executed on behalf of an event handler. |
...
Components
Universal Event Monitor Manager for Windows Universal Event Monitor Server for UNIX
