Mullen, Patrick <[EMAIL PROTECTED]> writes:
> Well, after grinding the heck out of my hard drive, I finally found both
> "shell-init" and "could not get current directory" in the same program.
> As should have been expected, they were from /bin/bash (and /bin/sh
> which is only a symbolic link to /bin/bash on RH6.1).
Something is using /bin/sh to run another program. When it does this,
it's doing so with a current directory set to a directory that the
program, given current permissions, can't read. bash is then complaining.
Chances are that somewhere there's a daemon being started from a directory
that, down the line, some other program running with different permissions
can't read. It's usually good to always start daemons with a current
directory of / to avoid this sort of problem.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
