Clarifications about sudo and secure_path #9
@@ -18,7 +18,14 @@ It moves files to a per-user _trash_ instead of permanently deleting them, while
|
|||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
**NOTE:** To use `resrm` with `sudo`, the path to `resrm` must be in the `$PATH` seen by `root`.\
|
**NOTE:** To use `resrm` with `sudo`, the path to `resrm` must be in the `$PATH` seen by `root`.\
|
||||||
Either install `resrm` as `root` (_preferred_), use `sudo -E resrm`, or add the `$PATH` to `/etc/sudoers` using its `Defaults secure_path` parameter.
|
Either:
|
||||||
|
|
||||||
|
* install `resrm` as `root` (_preferred_), or
|
||||||
|
* add the path to `resrm` to the `secure_path` parameter in `/etc/sudoers`. For example, where `/home/user/.local/bin` is where `resrm` is:
|
||||||
|
|
||||||
|
``` bash
|
||||||
|
Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/user/.local/bin"
|
||||||
|
```
|
||||||
|
|
||||||
Install via PyPI (_preferred_):
|
Install via PyPI (_preferred_):
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user