On Wed, 2016-11-16 at 14:19 +, Samuel Rakitničan wrote:
> > Am 16.11.2016 08:08, schrieb Samuel Rakitničan:
> >
> > You can change the default behaviour in "/etc/sudoers" or (better)
> > by adding a file in "/etc/sudoers.d".
> >
> > If you want to keep the users path, add:
> >
> > Defaults e
> Am 16.11.2016 08:08, schrieb Samuel Rakitničan:
>
> You can change the default behaviour in "/etc/sudoers" or (better) by
> adding a file in "/etc/sudoers.d".
>
> If you want to keep the users path, add:
>
> Defaults env_keep += "PATH"
> Defaults !secure_path
>
> or to change the (default) s
Am 16.11.2016 08:08, schrieb Samuel Rakitničan:
On Tue, 2016-11-15 at 18:42 +, Samuel Rakitničan wrote:
What about -E option?
Thanks for that, didn't take this into consideration. -E option
however seems to have no effect on PATH environment variable.
$ sudo -E env | grep ^PATH
PATH=/sbin
> On Tue, 2016-11-15 at 18:42 +, Samuel Rakitničan wrote:
>
> What about -E option?
Thanks for that, didn't take this into consideration. -E option however seems
to have no effect on PATH environment variable.
$ sudo -E env | grep ^PATH
PATH=/sbin:/bin:/usr/sbin:/usr/bin
Following however
On Tue, 2016-11-15 at 18:42 +, Samuel Rakitničan wrote:
> Hi,
>
> Something I stumbled upon today is that there is no convenient way by default
> to make some custom
> script accessible via sudo without specifying full path.
What about -E option?
> Found out that sudo have limited set of pa
