To-be 41 WP1: a shell that refuses logins need not be listed; giving back is never fatal
This commit is contained in:
@@ -100,7 +100,11 @@ against WP2's controller before anything is published.
|
||||
shell is still the one the mesh set, and the recorded shell is still executable, the recorded shell
|
||||
is set back. Otherwise the shell is left as it is, and the outcome says why.
|
||||
- Before a shell is set, it is refused unless it is executable and listed among the machine's shells.
|
||||
The refusal fails that resource and leaves the account untouched.
|
||||
The exception is a shell that refuses logins (`nologin`, `false`): the distribution does not list
|
||||
those, and the controller's own account uses one, so it need only be executable. The refusal fails
|
||||
that resource and leaves the account untouched.
|
||||
- Giving the shell back is reported, never fatal. A failed `usermod` on removal is named in the
|
||||
outcome and the record is dropped, because a fatal removal is exactly the wedge issue 225 is about.
|
||||
|
||||
**Proof.** The host's tests:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user