Rich Shepard <[email protected]> writes:
> This may have something to do with those orphan files I am dealing with,
> since it's come up only since those files appeared.
>
> Whenever I run 'find / -name ...' the last line returned is,
> find: Warning: file `ask.c' appears to have mode 0000
>
> I cannot find any file named ask.c and I suspect that mode 0000 makes it
> (virtually?) impossible to do so.
If that was true then find couldn't have told you which file it was; what is
presumably true is that it isn't trivial to locate it. (What that says is the
individual file has that mode, but the directory that contains it does not,
for reference. :)
However, try 'locate ask.c' and see what that turns up. Failing that, you can
use a very big hammer:
find / -ls 2>&1 | fgrep ask.c
That should give you the full path to the troublesome file.
[...]
> [r...@salmo ~]# chmod 666 ask.c
> chmod: cannot access `ask.c': No such file or directory
Nah, that just means you don't know the full path to it, and that find is
giving a less-than-helpful error message. If you apply that to the file in
whatever location it actually exists you should get the right outcome.
> I believe the mode 0000 makes it untouchable. I'll bet that's the mode of
> the other orphaned files, too.
>
> Must be the hard drive on its way out.
I would guess that, or lingering damage from the same.
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
