``ncheck -s'' sometimes misses security-relevant files

Paul Eggert eggert at sm.unisys.com
Fri Dec 30 07:14:30 AEST 1988


[Sorry about submitting the ncheck note twice -- I thought my mailer lost it.]

Regarding 'find', compared to 'ncheck -s':

    [[ It's just a little slower (even if ncheck worked correctly).  --wnl ]]

I also thought 'find' was slower than 'ncheck -s'.  But when I measured
them, 'ncheck -s' took 25% more wallclock time than the roughly equivalent
'find', and 60% more user+system CPU time (SunOS 4.0, Sun-3/160, Xylogics
7053, Toshiba MK251, 156 MB partition).  In comp.unix.wizards
<2802 at pixar.UUCP>, Rick Ace reports that 'ncheck' is unnecessarily buggy
and slow.  Until Sun fixes 'ncheck', stick to 'find'.



More information about the Comp.sys.sun mailing list