I have noticed that there are a great many enquiries concerning...
shell-init: could not get current directory: getcwd: cannot access parent
directories: No such file or directory
This can happen when mounting a disk onto a mount point that does not have
the correct underlying permissions set
"Kurc, Marcin A." wrote:
>
> how do you remove it?
> dpkg --purge package-name?
Yes, I do dpkt -P cracklib-runtime on both machines, then I do dpkg -P
cracklib2 on both machines, and then I reinstall with apt-get install
cracklib2 and apt-get install cracklib-runtime.
On the purge, the machine t
"Kurc, Marcin A." wrote:
>
> Try to install not from the directory that is removed while
Good point. The shell-init messages have now gone away, but I still
run:
apt-get install cracklib-runtime
for only a few seconds and I get no /var/cache/cracklib/*_dict.* files.
Again, this works
not get current directory
On my machine that's not doing PAM, I'm noticing after I took out
cracklib-runtime and cracklib2, and then try to reinstall cracklib2, I
get a bunch of diagnotic messages saying:
shell-init: could not get current directory: getcwd: cannot access
parent direc
On my machine that's not doing PAM, I'm noticing after I took out
cracklib-runtime and cracklib2, and then try to reinstall cracklib2, I
get a bunch of diagnotic messages saying:
shell-init: could not get current directory: getcwd: cannot access
parent directories: No such file or dire
>>>>> "Alexander" == Alexander Wallace <[EMAIL PROTECTED]> writes:
Alexander> shell-init: could not get current directory: getcwd: cannot
Alexander> access parent directories: No such file or directory
This either means your current directory has been dele
Hello there! I just installed woody on one of my servers, and everytime
i do something like with apt-get or restarting a service or almost any
other thing i get the following message:
shell-init: could not get current directory: getcwd: cannot access
parent directories: No such file or directory
7 matches
Mail list logo
