10 messages in net.sourceforge.lists.courier-users[courier-users] Re: shell-init: could...
FromSent OnAttachments
TWC | Mario PeschelAug 8, 2003 2:26 am 
Mitch (WebCob)Aug 8, 2003 8:51 am 
TWC | Mario PeschelAug 11, 2003 1:09 am 
Mitch (WebCob)Aug 11, 2003 1:17 am 
TWC | Mario PeschelAug 11, 2003 1:28 am 
Mitch (WebCob)Aug 11, 2003 1:36 am 
TWC | Mario PeschelAug 11, 2003 1:41 am 
Mitch (WebCob)Aug 11, 2003 1:43 am 
Sam VarshavchikAug 11, 2003 4:03 am 
Tim HunterAug 11, 2003 4:17 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: shell-init: could not get current directory: getcwd: cannot access parent directories: Permission deniedActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Aug 11, 2003 4:03:41 am
List:net.sourceforge.lists.courier-users

TWC | Mario Peschel writes:

I think this is correct, too. . . . bash-2.05# cd /mail/mario bash-2.05# ls -aln total 8 drwx------ 3 666 666 512 Aug 7 10:51 . drwxr-xr-x 41 666 666 1024 Aug 7 10:51 .. -rw------- 1 666 666 825 Jul 16 09:37 .mailfilter drwx------ 25 666 666 1024 Aug 11 10:17 Maildir

No, it's not. The explicit numeric ID in 'ls' indicates that this userid/groupid is not in your passwd file.

Running any shell script in this situation will result in bizarre diagnostic messages, such as the one you're seeing. Depending on the shell, it needs to read $HOME/.profile, or $HOME/.bashrc, before it begins working on the shell script. Naturally, if the shell can't find its uid in the passwd file, it will rightfully complain in the manner that you've observed.

Solution: put 666/666 in the passwd/group files.