Weird find Command Behavior 1

[Michael42]

Hello,

In a Sun Solaris 8 environment using the Bourne shell scripts I commonly use the find command as show below:

find /mydir -name "*.ARC" -type f -mtime +5

On one system Sun Solaris 8 system however when I issue the above find I am getting the message: "find: cannot read dir /mydir/lost+found: Permission denied"

If I remove the -mtime +5 parameter it works fine, i.e. I have files that are displayed in my directory. I am so stumped because this works on other systems.

What can you recommend?

Thanks,

Michael42

 

[PHV]

As root:
chmod ugo+rx /mydir/lost+found

Then you'll never have permission denied to read that directory.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[LKBrwnDBA]

Or justt re-direct the error to a null file:

find /mydir -name "*.ARC" -type f -mtime +5 2>/dev/null

----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

 

[Michael42]

The funcky thing is that when my find breaks because it cannot deal with the lost+found directory my script does too. Because of this just outputing to standard error does not seem to be effective (thanks LKBrwnDBA).

I cannot have the permissions changed at this time (thanks PHV).

Can anyone please detail how to use the find command to exclude the /mydir/lost+found directory from a find command with the criteria\example above?

Thanks very much for helping me pound this one out,

Michael

 

[PHV]

You may try this:
find `ls -d /mydir/* | grep -v lost+found` -name '*.ARC' -type f -mtime +5

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[Michael42]

PHV,

That rocked!

Thanks very much for posting,

Michael42

 

[SamBones]

That may be a workaround, but it doesn't answer the question why this is happening.

Can you check to see if you have the command "[tt]set -e[/tt]" in any of your startup scripts? That will cause the shell to exit if it hits any error. Type "[tt]echo $-[/tt]" and see if an "[tt]e[/tt]" is listed.

There MUST be some difference between this machine and the others (and mine).

 

[stefanwagner]

just another workaround:

find /mydir -not -regex "/mydir/lost+found.*" -name  '*.ARC' -type f -mtime +5

seeking a job as java-programmer in Berlin:

http://home.arcor.de/hirnstrom/bewerbung