Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-19 Thread Patrick Schoenfeld
Hi, On Tue, Nov 18, 2008 at 06:32:17PM +0100, Kai Weber wrote: I tried to run sudo in gdb and step through the code, but I failed. Maybe you have a tip? I stepped a bit through the code today and what I can get is that the message (not found) comes from sudo. The problem seems to be that in

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-19 Thread Patrick Schoenfeld
Hi Kai, On Tue, Nov 18, 2008 at 06:32:17PM +0100, Kai Weber wrote: It's exactly the same configuration. I again ask you: Really? Is it really that the group you configured in sudoers is in fact the group sudo? Or could it be that you use another group instead of sudo? I'm asking because I just

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-19 Thread Patrick Schoenfeld
Hi, hopefully this will be my last email for today :-) On Wed, Nov 19, 2008 at 01:39:00PM +0100, Patrick Schoenfeld wrote: I'm asking because I just figured that the problem seems to be related to the sudo group. If the user is not a member of the sudo group (which seems to have some special

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-19 Thread Kai Weber
... this indeed fixes the bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-19 Thread Kai Weber
This is reproducible for me, so I guess you in fact have different group memberships on the system where it works? I never thought that %adm ALL=(ALL) ALL and %sudo ALL=(ALL) ALL are THAT much different. But you are right. This is the cause of the bug. Regards, Kai --

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-19 Thread Patrick Schoenfeld
On Wed, Nov 19, 2008 at 04:12:27PM +0100, Kai Weber wrote: ... this indeed fixes the bug. Great. :-) I guess its _still_ a bug in Etch. But I think it does need no solving, because its easy fixable by a simple reconfiguration. Luckily we have this bug report open for documentation, if other

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-18 Thread Patrick Schoenfeld
Hi Kai, On Fri, Nov 14, 2008 at 05:06:01PM +0100, Kai Weber wrote: So I guess your problem is different and I wonder weither you have special options in your sudoers file. Can you attach it? I think that the defaults would be especially interesting. My settings are Debian standard

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-18 Thread Kai Weber
Can you please confirm this? On a system where it works, do you really have the exact same configuration wtr to sudo? It's exactly the same configuration. I'm out of options, too, so lets try more absurd things.. what shell does the user have, whose trying to run invoke-rc.d? What shell

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-14 Thread schoenfeld / in-medias-res
Tags 504580 +unreproducible thanks Hi, I tried to reproduce your bug [1] with the current version of sudo and the version you used back when your reported the bug. Unfortunately I was unable to do so. Could you report weither you still face this problem? Because if you don't face this problem

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-14 Thread Kai Weber
Since opening the bug, no new version of sudo for stable/etch was released. So I am still seeing this problem with sudo version 1.6.8p12-4. Maybe, you have an idea what I could try to debug the problem. Regards, Kai -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-14 Thread Patrick Schoenfeld
Hi, On Fri, Nov 14, 2008 at 12:20:04PM +0100, Kai Weber wrote: Since opening the bug, no new version of sudo for stable/etch was released. So I am still seeing this problem with sudo version 1.6.8p12-4. I didn't mean that it would be fixed by a new version in Etch (which is quiet unlikely

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-14 Thread Kai Weber
I didn't mean that it would be fixed by a new version in Etch (which is quiet unlikely given that we do not provide new versions in stable releases, but security fixes only) but it could be fixed in the next release of Debian. The current focus is on releasing Lenny, I understand. But in my

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-14 Thread Patrick Schoenfeld
Hi, On Fri, Nov 14, 2008 at 04:00:46PM +0100, Kai Weber wrote: I didn't mean that it would be fixed by a new version in Etch (which is quiet unlikely given that we do not provide new versions in stable releases, but security fixes only) but it could be fixed in the next release of

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-14 Thread Kai Weber
So I guess your problem is different and I wonder weither you have special options in your sudoers file. Can you attach it? I think that the defaults would be especially interesting. My settings are Debian standard settings: Defaultsenv_reset rootALL=(ALL) ALL %sudo ALL=(ALL)

Bug#504580: sudo: Commands in PATH /usr/sbin, /sbin not found

2008-11-05 Thread Kai Weber
Package: sudo Version: 1.6.8p12-4 Severity: normal I can not invoke commands in /usr/sbin, /sbin anymore. I have not found any difference in my setup to other machines I have. I disabled all .bashrc/.profile/... files to check if some configuration in there is doing harm. I tried to strace