search for: bash_env

...poolss.printer was failing at source3/script/tests/printing/modprinter.pl(138) with the Perl error in subject: Insecure $ENV{ENV} while running setgid at /home/user/src/samba-git/samba/source3/script/tests/printing/modprinter.pl line 138 code is: ============================== delete @ENV{'BASH_ENV'}; $ENV{'PATH'} = '/bin:/usr/bin'; # untaint PATH system("cp", "$tmp", "$smb_conf_file"); <== FAILING HERE unlink $tmp; ============================== the solution is, in addition to untainting $PATH: ============================== # the follow...

Hi, I'd like to access and modify shell environment variables before executing a command on a remote host via ssh. Unfortenatly, I can't figure out the proper way to do this... It seems, standard shell configuration files (e.g. ~/.bash_profile) are not sourced before ssh executes a command. Of course I could explicitly source them, e.g. ssh user at host 'source ~/.bash_profile;

...r/bin/pwd is not actually called, because of presence of builtin. We should disable that builtin to get everything work. Well, we can done it executing "enable -n pwd" in .bashrc script. But this won't work, since configure scripts are executing in non-interactive mode. We can set up BASH_ENV environmental variable to point to some script, which will be called during initialize. But this again won't work. Configure's are executing in "bash-as-sh" mode. It ignores BASH_ENV variable and even more - it ignores ENV variable, which should work as BASH_ENV in this case. Tha...

...n't call setsid as pid 1. The hack that I got to work (for reference, I'm using this for raw kernel testing qemu-kvm) is: kernel command line: init=/boot/mz-boot.sh $ cat /boot/mz-boot.sh #!/bin/bash main() { echo 'Init (hostname, HOSTNAME, INPUTRC, HOME, LOGNAME, USER, USERNAME, BASH_ENV, TERM, proc, fsck)' hostname linuxvm export HOSTNAME=linuxvm export INPUTRC=/etc/inputrc export HOME=/root export LOGNAME=root export USER=root export USERNAME=root export BASH_ENV=/root/.bashrc export TERM=xterm mount -t proc proc /proc fsck /dev/sda1 fsck /dev/sda3...

....7p1 to 5.1p1. Now bash no longer executes .bashrc when a user starts a non-interactively ssh session. Note that this is for Solaris 9 and 10. >From the bash man page (under INVOCATION): "When bash is started non-interactively, to run a shell script, for example, it looks for the variable BASH_ENV in the environment, expands its value if it appears there, and uses the expanded value as the name of a file to read and execute." If I set BASH_ENV in ~/.ssh/environment (and set PermitUserEnvironment to "yes" in sshd_config) then I can run any file I specify. Setting this option,...

H. Peter Anvin dixit: >But is that really a tty, then? I also understand that virtio console Hm. Both eglibc and dietlibc return true for isatty on it. >doesn't support termios, which makes this an ugly bifurcation. All of Let me test that? quick? hah not really (CONFIG_VIRTIO_CONSOLE=m)? ok luckily Ubuntu?s linux-image-3.15.0-5-generic is installable on Debian stable and has

Hi all, Just noted this behavior in the past couple of days, where if R is started in a shell script such as: gnome-terminal [-e][-x] R or in ESS (version 5.2.12 with Emacs or XEmacs), the LD_LIBRARY_PATH environment variable is not properly appended to, resulting in the loss of the pre-start value. This is using R Version 2.2.1 Patched (2006-02-28 r37448) on FC4. I noted this when

This might be a bit OT, but I've never had to do this before and what I've googled doesn't seem to be working. I have an ansible playbook that I'm working on that I want to run as a cronjob.? One task I'm having trouble with is where I have a text file with lines like: rd.pl "blah blah" rd.pl "blah blah blah" This text file has to be 'executed'

Everything seems to work, though I still have trouble with scp. The behaviour is not protocol dependent - acts the same with either. (Using RedHat 6.2) When I scp <file> <host>:<dir>, bash is invoked as a login shell on the server side host - this doesn't seem right. With my /etc/profile, I get Dec 6 15:06:20 amethyst sshd[3027]: error: select: Bad file descriptor in

...j=01;31: *.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:* .bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;3 5:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35: MACHTYPE=i386-redhat-linux-gnu MAIL=/var/spool/mail/root INPUTRC=/etc/inputrc BASH_ENV=/root/.bashrc LANG=en_US JAVA_HOME=/usr/local/jdk1.3.1_01 LOGNAME=root SHLVL=1 SHELL=/bin/bash USERNAME=root HOSTTYPE=i386 OSTYPE=linux-gnu HISTSIZE=1000 HOME=/root TERM=xterm PATH=/usr/local/jdk1.3.1_01/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/u sr/local/bin:/usr/X11R6/bin:/tmp/status/te...

...mp;2 exit 1 fi # Unset variables that we do not need and which cause bugs (e.g. in # pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1" # suppresses any "Segmentation fault" message there. '((' could # trigger a bug in pdksh 5.2.14. for as_var in BASH_ENV ENV MAIL MAILPATH do eval test x\${$as_var+set} = xset \ && ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || : done PS1='$ ' PS2='> ' PS4='+ ' # NLS nuisances. LC_ALL=C export LC_ALL LANGUAGE=C export LANGUAGE # CDPATH. (unset...