Tom,
thanks very much for your answer. Ok, Roger already gave me the hint
with the secure_path option. However thanks for the advice with
displaying sudo's PATH environment.
Steve.
On 29.12.2011 20:41, Tom H wrote:
On Thu, Dec 29, 2011 at 11:15 AM, Steve Kreyer wrote:
after an update of m
On Thu, Dec 29, 2011 at 11:15 AM, Steve Kreyer wrote:
>
> after an update of my Debian system some time ago I've encountered some
> problems with sudo. In particular sudo doesn't seem to recognize any
> commands located in /sbin or /usr/sbin. For example the command useradd is
> located in /usr/sb
On Jo, 29 dec 11, 18:50:03, Steve Kreyer wrote:
> Roger,
>
> thanks very much for your answer. Yes, the two lines solve the
> problem. I was working with "sudo su" for days till I asked here.
> Thanks for saving me further hard typing work. :-)
Just for the archives: you can replace 'sudo su' wit
Roger,
thanks very much for your answer. Yes, the two lines solve the problem.
I was working with "sudo su" for days till I asked here. Thanks for
saving me further hard typing work. :-)
Steve
On 29.12.2011 17:16, Roger Leigh wrote:
On Thu, Dec 29, 2011 at 05:15:19PM +0100, Steve Kreyer wr
On Thu, Dec 29, 2011 at 05:15:19PM +0100, Steve Kreyer wrote:
> after an update of my Debian system some time ago I've encountered
> some problems with sudo. In particular sudo doesn't seem to
> recognize any commands located in /sbin or /usr/sbin.
[…]
> What could be wrong here? Can I somehow see
Hi all,
after an update of my Debian system some time ago I've encountered some
problems with sudo. In particular sudo doesn't seem to recognize any
commands located in /sbin or /usr/sbin. For example the command useradd
is located in /usr/sbin and sudo fails:
redwing@platon:~$ sudo usera
6 matches
Mail list logo
