Linux List All Files

0 Likes

This tool lists all files on an NSS Volumes on an OES Linux Server, it also lists the file ids, modified time, size, and whether the object is a directory.



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 list the files on an NSS Volume in an XML output 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:


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



From a terminal prompt type: Perl linuxListAllFiles.pl <enter>



A sample output would be the following:



grep57:/a # perl linuxListAllFiles.pl NSS1
file is now open
File Name: </_admin/Manage_NSS/Volume/NSS1/FileEvents.xml
Request Sent: <nssRequest><fileEventList><listAllFiles/></fileEventList></nssRequest>
<nssReply>
<fileEventList>
<listAllFiles>
<file><name><![CDATA[\]]></name><id1>127</id1><id2>0</id2><id3>0</id3><modifiedTime>20061117141938</modifiedTime><size>0</size><directory/></file>
<file><name><![CDATA[\._NETWARE]]></name><id1>128</id1><id2>0</id2><id3>0</id3><modifiedTime>20060914125736</modifiedTime><size>0</size><directory/></file>
<file><name><![CDATA[\filecheck.pl]]></name><id1>144</id1><id2>0</id2><id3>0</id3><modifiedTime>20061117141937</modifiedTime><size>879</size></file>
<file><name><![CDATA[\linuxListEpochs.pl]]></name><id1>145</id1><id2>0</id2><id3>0</id3><modifiedTime>20061117141938</modifiedTime><size>1705</size></file>
<file><name><![CDATA[\linuxListFileEvents.pl]]></name><id1>146</id1><id2>0</id2><id3>0</id3><modifiedTime>20061117141938</modifiedTime><size>1713</size></file>
<file><name><![CDATA[\linuxStartEventEpoch.pl]]></name><id1>147</id1><id2>0</id2><id3>0</id3><modifiedTime>20061117141938</modifiedTime><size>1711</size></file>
<file><name><![CDATA[\linuxStopEventEpoch.pl]]></name><id1>148</id1><id2>0</id2><id3>0</id3><modifiedTime>20061117141938</modifiedTime><size>2067</size></file>
<file><name><![CDATA[\._NETWARE\.trustee_work.dat]]></name><id1>347</id1><id2>0</id2><id3>0</id3><modifiedTime>20060914125736</modifiedTime><size>0</size></file>
<file><name><![CDATA[\._NETWARE\.trustee_database.xml]]></name><id1>279314</id1><id2>0</id2><id3>0</id3><modifiedTime>20060914125736</modifiedTime><size>2587</size></file>
<result value="0"><description>zOK</description></result>
</listAllFiles>
</fileEventList>
</nssReply>


The specifications explain the XML tags, but the information present here would let someone know the file or directory found on the NSS volume, the file name, file ID, modified time, and file size.

Labels:

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