Nsscash is very careful when deploying the changes:
- All files are updated using the standard "write to temporary file", "sync",
Nsscash is very careful when deploying the changes:
- All files are updated using the standard "write to temporary file", "sync",
- All errors cause an immediate abort ("fail fast") with a proper error
message and a non-zero exit status. This prevents hiding possibly important
errors. In addition all files are fetched first and then deployed to try to
- All errors cause an immediate abort ("fail fast") with a proper error
message and a non-zero exit status. This prevents hiding possibly important
errors. In addition all files are fetched first and then deployed to try to
when all operations were successful.
- To prevent unexpected permissions, `nsscash` does not create new files. The
user must create them first and `nsscash` will then re-use the permissions
when all operations were successful.
- To prevent unexpected permissions, `nsscash` does not create new files. The
user must create them first and `nsscash` will then re-use the permissions
- To prevent misconfigurations, empty files (no users/groups) are not
permitted and will not be written to disk. This is designed to prevent the
accidental loss of all users/groups on a system.
- To prevent misconfigurations, empty files (no users/groups) are not
permitted and will not be written to disk. This is designed to prevent the
accidental loss of all users/groups on a system.
- C compiler, for `libnss_cash.so.2`
Tested on Debian Stretch and Buster, but should work on any GNU/Linux system.
- C compiler, for `libnss_cash.so.2`
Tested on Debian Stretch and Buster, but should work on any GNU/Linux system.