INFO: Your private directory has been unmounted.
INFO: To see this change in your current shell:
cd /home/kipras
```
and then manually re-mounting the home directory:
```bash
$ ecryptfs-mount-private
Enter your login passphrase:
Inserted auth tok with sig [THE_SIGNATURE] into the user session keyring
INFO: Your private directory has been mounted.
INFO: To see this change in your current shell:
cd /home/kipras
```
Everything seems to work. However, if I launch another terminal, I get the following error:
```
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
```
If I `cd ~`, the terminal works fine as expected. BUT, if I launch another terminal - the same `shell-init` error comes up. It keeps happening every time I open a new terminal.
---
Also, this is probably not related since this comes from NodeJS, but I also get these errors together with the `shell-init` error:
```
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
path.js:975
const path = i >= 0 ? args[i] : process.cwd(); ^
Error: ENOENT: no such file or directory, uv_cwd
at Object.resolve (path.js:975:47)
at Function.Module._resolveLookupPaths (internal/modules/cjs/loader.js:550:17)
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:648:20)
at Function.Module._load (internal/modules/cjs/loader.js:580:25)
at Module.require (internal/modules/cjs/loader.js:711:19)
at require (internal/modules/cjs/helpers.js:14:16)
at /home/kipras/.config/nvm/versions/node/v11.13.0/lib/node_modules/npm/bin/npm-cli.js:19:21
at Object.<anonymous> (/home/kipras/.config/nvm/versions/node/v11.13.0/lib/node_modules/npm/bin/npm-cli.js:153:3)
at Module._compile (internal/modules/cjs/loader.js:805:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:816:10)
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run `nvm use --delete-prefix v11.13.0 --silent` to unset it.
```
After manually unmounting the home directory:
```bash umount- private
cd /
$ ecryptfs-
Sessions still open, not unmounting
$ ecryptfs- umount- private
INFO: Your private directory has been unmounted.
INFO: To see this change in your current shell:
cd /home/kipras
```
and then manually re-mounting the home directory:
```bash mount-private
$ ecryptfs-
Enter your login passphrase:
Inserted auth tok with sig [THE_SIGNATURE] into the user session keyring
INFO: Your private directory has been mounted.
INFO: To see this change in your current shell:
cd /home/kipras
```
Everything seems to work. However, if I launch another terminal, I get the following error:
```
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
```
If I `cd ~`, the terminal works fine as expected. BUT, if I launch another terminal - the same `shell-init` error comes up. It keeps happening every time I open a new terminal.
---
Also, this is probably not related since this comes from NodeJS, but I also get these errors together with the `shell-init` error:
```
^
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
path.js:975
const path = i >= 0 ? args[i] : process.cwd();
Error: ENOENT: no such file or directory, uv_cwd Module. _resolveLookupP aths (internal/ modules/ cjs/loader. js:550: 17) Module. _resolveFilenam e (internal/ modules/ cjs/loader. js:648: 20) Module. _load (internal/ modules/ cjs/loader. js:580: 25) modules/ cjs/loader. js:711: 19) modules/ cjs/helpers. js:14:16) .config/ nvm/versions/ node/v11. 13.0/lib/ node_modules/ npm/bin/ npm-cli. js:19:21 kipras/ .config/ nvm/versions/ node/v11. 13.0/lib/ node_modules/ npm/bin/ npm-cli. js:153: 3) modules/ cjs/loader. js:805: 30) Module. _extensions. .js (internal/ modules/ cjs/loader. js:816: 10)
at Object.resolve (path.js:975:47)
at Function.
at Function.
at Function.
at Module.require (internal/
at require (internal/
at /home/kipras/
at Object.<anonymous> (/home/
at Module._compile (internal/
at Object.
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run `nvm use --delete-prefix v11.13.0 --silent` to unset it.
```