Very Computer

by **Mat** » Sun, 21 Sep 1997 04:00:00

Hi,

I'm having problems with my users (and my weekly run output) getting
errors like:

shell-init: could not get current directory: getcwd: cannot access
parent directories

job-working-directory: could not get current directory: getcwd: cannot
access parent directories

(they're from the "rebuilding locate database" section of my weekly run
output)

My users also get similar errors when logging in, changing dirs, listing
dirs, etc. It doesn't cause problems ALL the time (a plain "cd" will
make it show the correct directory in the prompt, etc) though the error
line is showed all the time.

I assume it's all do with getcwd. Anyone know why this is happening? If
so, please Cc a reply to my email address. Thanks.

Cya,

--
Matt Bruce

NB: Remove X's to email me (anti-spam)

by **J Wuns** » Sun, 21 Sep 1997 04:00:00

> I'm having problems with my users (and my weekly run output) getting
> errors like:

> shell-init: could not get current directory: getcwd: cannot access
> parent directories

Unless somebody really removed the current working directory of the
process while it was running (which is possible), the best suspicion
would be that one of your mointpoints (like /usr) has mangled
permissions. That's nothing you could see while something is mounted
on it. Bott single-user, and make sure all mount points have at least
permissions 555.

--
cheers, J"org

Never trust an operating system you don't have sources for. ;-)

by **Conrad Sabati** » Thu, 25 Sep 1997 04:00:00

>> I'm having problems with my users (and my weekly run output) getting
>> errors like:

>> shell-init: could not get current directory: getcwd: cannot access
>> parent directories

>Unless somebody really removed the current working directory of the
>process while it was running (which is possible), the best suspicion
>would be that one of your mointpoints (like /usr) has mangled
>permissions. That's nothing you could see while something is mounted
>on it. Bott single-user, and make sure all mount points have at least
>permissions 555.

I had the same problem a while back after I had gone a bit overboard with
permission settings (trying to tighten security), and in addition to
correcting the permissions as Joerg says, I also modified each user's
profile (not their ~/.profile file, but their /etc info) to use
/usr/home/whatever instead of the symlink /home/whatever. Not sure if the
latter was really necessary, though.
--
Conrad Sabatier | FreeBSD -- UNIX for your PC
http://www.neosoft.com/~conrads | Why settle for less than the best?

Very Computer

What's causing "getcwd" errors?

What's causing "getcwd" errors?

What's causing "getcwd" errors?

What's causing "getcwd" errors?