This utility will stop an existing active EFL epoch and start a new active epoch for a specified NSS volume. All files whos data or metadata is changed after the start of the new epoch will be added to the EFL for that 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:

linuxChangeEventEpoch.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. This Utility requires the user to enter the 37 digit active epoch number. The number is displayed in the text above the input line. The user must enter the entire number complete with dashes. RELATED: linuxStoptEventEpoch.pl or the linuxListEpochs.pl, and linuxStartEventEpoch.pl, linuxListFileEvents.pl

To run the perl script type:

perl linuxChangeEventEpoch.pl VOLUME_NAME <enter>

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

Example: perl linuxResetEventList.pl VOL1 <enter>

Sample output:

grep57:/a # perl linuxChangeEventEpoch.pl NSS1
file is now open </_admin/Manage_NSS/Volume/NSS1/FileEvents.xml
<nssRequest><fileEventList><listEpochs/></fileEventList></nssRequest>
<nssReply>
<fileEventList>
<listEpochs>
<activeEpochs>
<epoch value="59668d9a-7f34-01db-80-00-993f4a82c9da"/>
</activeEpochs>
<usedEpochs>
<epoch value="59668d9a-7f34-01db-80-00-993f4a82c9da"/>
</usedEpochs>
<result value="0"><description>success</description></result>
</listEpochs>
</fileEventList>
</nssReply>

Choose an epoch and type in the complete 37 letter code including dashes.

59668d9a-7f34-01db-80-00-993f4a82c9da
 </_admin/Manage_NSS/Volume/NSS1/FileEvents.xml
<nssRequest><fileEventList><changeEventEpoch epochNumber="59668d9a-7f34-01db-80-00-993f4a82c9da"/></fileEventList></nssRequest>
<nssReply>
<fileEventList>
<changeEventEpoch>
<epoch value="59668d9a-7f34-01db-80-00-993f4a82c9da"/>
<newEpoch value="4a4f8340-7fc8-01db-80-00-993f4a82c9da"/>
<result value="0"><description>success</description></result>
</changeEventEpoch>
</fileEventList>
</nssReply>

The specifications explain the XML tags.