This tool stops an active EFL epoch. It uses the Virtual File Services (Originally called Virtual File Services for NetWare) which were ported over to Linux. The SDK for this API set can be downloaded from http://developer.novell.com/wiki/index.php/Virtual_File_Services_for_NetWare. The objective of the tool is to add a trustee to a file using XML as specified in the VFS for NetWare specification. It is intended to be used as a sample script for developers that may want to use the VFS API set to view and manage storage.

How to Use the file:

linuxStopEventEpoch.pl is a Perl script. So Perl must be installed and running on the Linux server that this file is being loaded on. NSS must be installed to get the VFS support. linuxStoptEventEpoch uses the stopEventEpoch API to stop the current EFL Epoch. RELATED: To start a new event epoch refer to the linuxStartEventEpoch.pl or the LinuxChangeEventEpoch.pl which will stop the active EFL Epoch and start a new one using the changeEventEpoch API.

To run the perl script type:

perl linuxStopEventEpoch.pl VOLUME_NAME <enter>

Where VOLUME_NAME is the name of the NSS volume where the active EFL Epoch is to be stopped.

The user will be prompted to type in one of the 37 digit Epoch Numbers displayed above the prompt. Type in one of the active Epochs or the utility will fail, then press enter.

Example: perl linuxStopEventEpoch.pl VOL1 <enter>

A sample output would be the following:

grep57:/a # perl linuxStopEventEpoch.pl NSS1
file is now open </_admin/Manage_NSS/Volume/NSS1/FileEvents.xml
<nssRequest><fileEventList><listEpochs/></fileEventList></nssRequest>
<nssReply>
<fileEventList>
<listEpochs>
<activeEpochs>
<epoch value="e5d831be-7680-01db-80-00-bd1cd5b47e57"/>
</activeEpochs>
<usedEpochs>
<epoch value="e5d831be-7680-01db-80-00-bd1cd5b47e57"/>
</usedEpochs>
<result value="0"><description>success</description></result>
</listEpochs>
</fileEventList>
</nssReply>

e5d831be-7680-01db-80-00-bd1cd5b47e57
 </_admin/Manage_NSS/Volume/NSS1/FileEvents.xml
<nssRequest><fileEventList><stopEventEpoch epochNumber="e5d831be-7680-01db-80-00-bd1cd5b47e57"/></fileEventList></nssRequest>
<nssReply>
<fileEventList>
<stopEventEpoch>
<epoch value="e5d831be-7680-01db-80-00-bd1cd5b47e57"/>
<result value="0"><description>success</description></result>
</stopEventEpoch>
</fileEventList>
</nssReply>

The specifications explain the XML tags.