>>>>> "Rich" == Rich Shepard <[email protected]> writes:
Carlos> If all else fails, run it in strace. That should tell you Carlos> exactly which file it fails to stat. Rich> I'm not educated sufficiently to understand the strace Rich> output. It ends this way: I run strace like so: strace -f -o /tmp/strace-foo <normal-commandline> The '-f' says follow any forks (if it spawns any children, trace them too), the '-o /tmp/strace-foo' says redirect the output to the filename you provide. When it finishes, open /tmp/strace-foo with /usr/bin/less and start hunting around for open() or similar calls that fail. Probably most expeditious to start at the bottom and work up. Strace generates lots of volume, a tiny fraction of which is very interesting, but your error is in there somewhere and by judicious guessing, you'll identify it before long. -- Russell Senior, President [email protected] _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
