Bob Proulx wrote:
> Paul Scott wrote:
> > I get:
> > sudo printenv PATH
> > /usr/local/bin:/usr/bin:/bin:/usr/games
>
> That is definitely bad and needs to be fixed. This is probably going
> to bite a lot of people. List, listen up, I predict this to be a
> recurring theme for a while. :-)
As
On Tue, 30 Aug 2011 12:32:16 -0700, Paul Scott wrote:
> Thanks! I have now purged and reinstalled sudo and everything seems to
> be working as I was used to.
You didn't need to do that. All you needed to do was to edit /etc/sudoers
as Bob suggested.
--
To UNSUBSCRIBE, email to debian-user-r
On 08/30/2011 11:56 AM, Bob Proulx wrote:
Paul Scott wrote:
Bob Proulx wrote:
What is your path after the sudo? This is easy to tell with:
sudo printenv PATH
I see this on my Sid machine:
$ sudo printenv PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
I get:
sudo p
On 08/30/2011 11:02 AM, David Goodenough wrote:
On Tuesday 30 Aug 2011, Paul Scott wrote:
Hi,
I'm running sid.
I have found several partial answers with Google but nothing conclusive.
About a week ago 'sudo aptitude' stopped working because /sbin and
/usr/sbin are no longer on the path. Is t
Paul Scott wrote:
> Bob Proulx wrote:
> >What is your path after the sudo? This is easy to tell with:
> > sudo printenv PATH
> >I see this on my Sid machine:
> > $ sudo printenv PATH
> > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>
> I get:
>
> sudo printenv PATH
> /usr/lo
On Tuesday 30 Aug 2011, Paul Scott wrote:
> Hi,
>
> I'm running sid.
>
> I have found several partial answers with Google but nothing conclusive.
>
> About a week ago 'sudo aptitude' stopped working because /sbin and
> /usr/sbin are no longer on the path. Is this possible a recent security
> im
On 08/30/2011 11:16 AM, Bob Proulx wrote:
Camaleón wrote:
Paul Scott wrote:
About a week ago 'sudo aptitude' stopped working because /sbin and
/usr/sbin are no longer on the path. Is this possible a recent security
improvement? Aptitude works fine if I use "su -" instead of sudo.
But surely
On 08/30/2011 10:43 AM, Camaleón wrote:
On Tue, 30 Aug 2011 10:02:58 -0700, Paul Scott wrote:
About a week ago 'sudo aptitude' stopped working because /sbin and
/usr/sbin are no longer on the path. Is this possible a recent security
improvement? Aptitude works fine if I use "su -" instead of
Camaleón wrote:
> Paul Scott wrote:
> > About a week ago 'sudo aptitude' stopped working because /sbin and
> > /usr/sbin are no longer on the path. Is this possible a recent security
> > improvement? Aptitude works fine if I use "su -" instead of sudo.
But surely aptitude is in /usr/bin/aptitude
On Tue, 30 Aug 2011 10:02:58 -0700, Paul Scott wrote:
> About a week ago 'sudo aptitude' stopped working because /sbin and
> /usr/sbin are no longer on the path. Is this possible a recent security
> improvement? Aptitude works fine if I use "su -" instead of sudo.
Hummm... the change seems to b
10 matches
Mail list logo