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 DISPLAY
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 DISPLAY and
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 drastic
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 using sudo?
setenv is not an external command such as can
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
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:
$ sudo export DISPLAY=`teufel`:0.0
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 DISPLAY is
Bonjour a tous :)
Je suis en train d'installer l'add on java JMF jusque la, pas de probleme
sauf que dans les instructions d'installation, ces gros malins ont encore dut
prevoir pour redhat
et donc voici 3 lignes a tapper dans mon shell :
setenv JMFHOME /home/someuser/JMF-2.1.1e
Le Jeudi 25 Novembre 2004 23:39, Pierre Ancelot a écrit :
setenv JMFHOME /home/someuser/JMF-2.1.1e
setenv CLASSPATH $JMFHOME/lib/jmf.jar:.:${CLASSPATH}
setenv LD_LIBRARY_PATH $JMFHOME/lib:${LD_LIBRARY_PATH}
c'est la version pour le shell csh (ou dérivés)
en bash ça donne :
export JMFHOME
donc voici 3 lignes a tapper dans mon shell :
setenv JMFHOME /home/someuser/JMF-2.1.1e
setenv CLASSPATH $JMFHOME/lib/jmf.jar:.:${CLASSPATH}
setenv LD_LIBRARY_PATH $JMFHOME/lib:${LD_LIBRARY_PATH}
C'est tres marrant MAIS
bash: setenv: command not found
normal, setenv n'est pas une syntaxe
slt,
D'après ce que j'ai compris suexec filtre une partie des setenv envoyés
dans le virtualhost.
Où puis-je trouver le détail de la configuration de suexec compilé pour
woody ?
Merci
--
William - http://flibuste.net
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 Frey [EMAIL PROTECTED
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 csh/tcsh. Apparently, you
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 bash the corresponding command
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, this I have in,
`/usr/include/bsd
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 `/usr/include
17 matches
Mail list logo