> On Wed, Mar 08, 2006 at 02:30:06PM -0500, Haines Brown wrote:
> > Andrew Cady <[EMAIL PROTECTED]> writes:
> >
> > > As others have pointed out, sudo does not by default preserve its
> > > environment when starting privileged processes. To get X working, you
> > > will want to have sudoers retai
On Wed, Mar 08, 2006 at 02:30:06PM -0500, Haines Brown wrote:
> Andrew Cady <[EMAIL PROTECTED]> writes:
>
> > As others have pointed out, sudo does not by default preserve its
> > environment when starting privileged processes. To get X working, you
> > will want to have sudoers retain both DISPL
On Mon, Mar 06, 2006 at 08:08:35AM -0500, Haines Brown wrote:
>
> $ env | grep DISPLAY.
> DISPLAY=:0.0
>
> $ sudo env | grep DISPLAY
> [nothing returned]
>
> Why do I get inconsistent results?
As others have pointed out, sudo does not by default preserve its
environment when start
At 1141715589, Hugo Vanwoerkom wrote:
> Jon Dowland wrote:
> >sudo no longer lets DISPLAY through without you telling
> >it to first: actually, sudo has changed from a blacklist
> >to a whitelist model for environment variables.
>
> good point. And that in Sarge = stable!
Yes - it was rather a d
Jon Dowland wrote:
On Mon, Mar 06, 2006 at 08:08:35AM -0500, Haines Brown wrote:
$ echo $DISPLAY
:0.0
$ sudo echo $DISPLAY
:0.0
That seemed OK, but when I did:
$ sudo env | grep DISPLAY
[nothing returned]
Why do I get inconsistent results? In the first case, the
val
On Mon, Mar 06, 2006 at 08:08:35AM -0500, Haines Brown wrote:
> $ echo $DISPLAY
> :0.0
>
> $ sudo echo $DISPLAY
> :0.0
> That seemed OK, but when I did:
> $ sudo env | grep DISPLAY
> [nothing returned]
> Why do I get inconsistent results? In the first case, the
> value of D
6 matches
Mail list logo
