On Fri, May 11, 2007 at 09:29:08AM +1000, RW wrote:
> In the past I have always applied relevant patches and recompiled
> whatever was needed to take care of errata items.
>
> Nearly a week ago I decided to use a spare machine to track i386 4.1
> stable, did what I was told (FAQ, thanks Nick et al!) : untarred
> sources, cvs updates, makes all went without hitches and just used a
> fair few hours.
>
> The build box now sends me email every day saying:
> Checking setuid/setgid files and devices:
> Setuid/device find errors:
> find: fts_read: No such file or directory
> I ran sh -v /etc/security 2>&1 |less and searched for fts_read but the
> context is just waht you'd expect from the output above.
> I know that fts_read is a part of find but what is it looking for in
> vain?
>
> I get an itchy feeling that everything did not go as expected during
> update but the box seems to do whatever I try with no problems.
Can you use debug 'echo' statements or somesuch to find out what command
causes it? It could indeed be find, although I haven't ever seen this
error message from find...
Joachim
--
TFMotD: rndc (8) - name server control utility
