Linux Ping Epoch

0 Likes

If an epoch is inactive for more than the default interval (determinable by linuxGetInactiveEpochInterval) then the epoch will be removed. Using this script to ping the epoch will reset the Inactive clock and begging the inactive interval again. 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:


linuxPingEpoch.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.



To run the perl script type:



per linuxPingEpoch.pl.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 linuxPingEpoch.pl.pl VOL1 <enter>



Sample output:



perl linuxPingEpoch.pl NSS1
file is now open </_admin/Manage_NSS/Volume/NSS1/FileEvents.xml
<nssRequest><fileEventList><listEpochs/></fileEventList></nssRequest>
<nssReply>
<fileEventList>
<listEpochs>
<activeEpochs>
<epoch value="999b2e58-8ee7-01db-80-00-7d12a3031248"/>
</activeEpochs>
<usedEpochs>
<epoch value="999b2e58-8ee7-01db-80-00-7d12a3031248"/>
</usedEpochs>
<result value="0"><description>success</description></result>
</listEpochs>
</fileEventList>
</nssReply>



Choose an epoch and type in the complete 37 letter code including dashes.
999b2e58-8ee7-01db-80-00-7d12a3031248
</_admin/Manage_NSS/Volume/NSS1/FileEvents.xml
<nssRequest><fileEventList><pingEpoch epochNumber="999b2e58-8ee7-01db-80-00-7d12a3031248"/></fileEventList></nssRequest>
<nssReply>
<fileEventList>
<pingEpoch>
<epoch value="999b2e58-8ee7-01db-80-00-7d12a3031248"/>
<result value="0"><description>success</description></result>
</pingEpoch>
</fileEventList>
</nssReply>


The specifications explain the XML tags.

Labels:

How To-Best Practice
Collateral
Comment List
Anonymous
Related Discussions
Recommended