> 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
rve its
environment when starting privileged processes. To get X working, you
will want to have sudoers retain both DISPLAY and XAUTHORITY.
> # sudo setenv DISPLAY teufel:0
>
> but I get the error, "command not found". Shouldn't it be accessible
> from a bash prompt when
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
the environment accessed by sudo.
At least something is wrong, so I set out to do (teufel is the host
name):
# sudo setenv DISPLAY teufel:0
but I get the error, "command not found". Shouldn't it be accessible
from a bash prompt when using sudo?
I suppose I could also do:
Hi Neil,
> Can someone kindly point me in the right direction
> to solve a niggling problem,
> When I do a `su' command bash comes up with
> an error message,
>
> bash: setenv : command not found
>
> I have a man page for setenv which refers
> to stdlib.h, th
> Can someone kindly point me in the right direction
> to solve a niggling problem,
> When I do a `su' command bash comes up with
> an error message,
>
> bash: setenv : command not found
the setenv command is built into the csh shell to set environment
variables, in
On Fri, 15 Nov 1996, Neil Walker wrote:
> Can someone kindly point me in the right direction
> to solve a niggling problem,
> When I do a `su' command bash comes up with
> an error message,
>
> bash: setenv : command not found
That's because setenv is built into cs
>bash: setenv : command not found
>
setenv is a C-shell builtin.
I guess, that you have probably set a C-shell variant as your login in
shell, but didn't wrote 'su -'.
My suggestion: Change your login shell to bash (chsh -s /bin/bash)
and try again.
David
--
David F
Thanks to all who responded, problem solved.
Some time ago I had a trouble with
with color-ls. I had put bash.rc's and bash_profile's
in /etc & /root csh.cshrc and so on
A clear out and fresh start has worked wonders,
Thanks again ,
Neil
--
~~
Can someone kindly point me in the right direction
to solve a niggling problem,
When I do a `su' command bash comes up with
an error message,
bash: setenv : command not found
I have a man page for setenv which refers
to stdlib.h, this I have in,
`/usr/include/bsd/stdlib.h' and `/u
13 matches
Mail list logo
