<font size=2 face="sans-serif">As always when dealing with computers and
potentially long running jobs, run a test on a handful of files first,
so you can rapidly debug.<br>Did you read the mmfind.README ?</font><br><br><font size=2 face="sans-serif">It mentions...that this sample utility
"some user assembly required..." ... </font><br><br><font size=2 face="sans-serif">mmfindUtil_processOutputFile.c</font><br><font size=2 face="sans-serif"> A utility to parse the "list
file" produced by mmapplypolicy and to print</font><br><font size=2 face="sans-serif"> it in a find-compatible
format</font><br><font size=2 face="sans-serif"> mmfind invokes it once mmapplypolicy
begins to populate the "list file"</font><br><br><font size=2 face="sans-serif">mmfindUtil_processOutputFile.sampleMakefile</font><br><font size=2 face="sans-serif"> copy to 'makefile', modify as
needed, and run 'make' to compile mmfindUtil_processOutputFile.c</font><br><font size=2 face="sans-serif"> This should produce a binary
called mmfindUtil_processOutputFile</font><br><font size=2 face="sans-serif"> mmfind will not be able to run
until this utility has been compiled</font><br><font size=2 face="sans-serif"> on the node from which you launch
mmfind.</font><br><font size=2 face="sans-serif"><br>Works for me...</font><br><font size=2 face="sans-serif">[root@n2 ilm]# ./mmfind /goo/zdbig -ls</font><br><font size=2 face="sans-serif">2463649 256 drwxr-xr-x
2 root root 262144 Feb 9 11:41
/goo/zdbig</font><br><font size=2 face="sans-serif">6804497 0 -rw-r--r--
1 root root 0 Feb
9 11:41 /goo/zdbig/xy</font><br><BR>