search for: all_proxy

...t;http://${PROXYHOST}:${PROXYPORT}" export https_proxy="http://${PROXYHOST}:${PROXYPORT}" export HTTPS_PROXY="http://${PROXYHOST}:${PROXYPORT}" export ftp_proxy="http://${PROXYHOST}:${PROXYPORT}" export FTP_PROXY="http://${PROXYHOST}:${PROXYPORT}" export all_proxy="http://${PROXYHOST}:${PROXYPORT}" export ALL_PROXY="http://${PROXYHOST}:${PROXYPORT}" export no_proxy="localhost,$(hostname -s),$(hostname -f),$(hostname -d),127.0.0.1" export NO_PROXY="localhost,$(hostname -s),$(hostname -f),$(hostname -d),127.0.0.1" export...

Hallo, what is the right way to set a proxy systemwide using centos 7? I need this for wget and docker. My first idea was /etc/environment but allthough the proxy is set wget and docker don? t connect to their target-systems. Thanks for hints Ralf

Dear all when I am login in terminal I am getting following message. declare -x ALL_PROXY="socks://hproxy.iitm.ac.in:3128/" declare -x AMBERHOME="/sware/amber/amber12" declare -x COLORTERM="gnome-terminal" declare -x CPPFLAGS="-I/usr/local/bin/include" declare -x DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-adjIuc8A5l,guid=d2289573889e3c...

Fix for: https://bugzilla.redhat.com/show_bug.cgi?id=1354507 Main explanation is in patch #3. Rich.

...side I'm doing: ssh -D1080 -A -J PUBLIC_SERVER root at 127.0.0.1 -p29022 then, I'm logged in into the device at home/10.10.0.1 So at this point, if I want to reach a device into the 10.10.0.1/24 network I'm doing (with tsocks): export LD_PRELOAD="/lib64/libtsocks.so" export all_proxy="socks5://127.0.0.1" ssh 10.10.0.2 and it always worked for me. At some point(recently) while the connection to home/10.10.0.1 worked as usual, I was not able to connect to 10.0.0.2 with an output like: ssh root at 10.10.0.2 -vvvv OpenSSH_9.6p1, OpenSSL 3.0.12 24 Oct 2023 debug1: Read...

Previously posted: https://www.redhat.com/archives/libguestfs/2018-November/msg00000.html https://www.redhat.com/archives/libguestfs/2018-November/msg00001.html This completes the split and rewrite of the virt-v2v manual to make it much simpler to understand and digest. Rich.

...nherit input_libvirt input_conn input_password guest + lazy_conn input_password parsed_uri server guest = +object (self) + inherit input_libvirt lazy_conn guest val saved_source_paths = Hashtbl.create 13 val mutable dcPath = "" @@ -61,12 +61,7 @@ object unsetenv "ALL_PROXY"; unsetenv "NO_PROXY"; - (* Get the libvirt XML. This also checks (as a side-effect) - * that the domain is not running. (RHBZ#1138586) - *) - let xml = Libvirt_utils.dumpxml ?password_file:input_password - ?conn:input_conn gu...

v2 was posted here: https://www.redhat.com/archives/libguestfs/2019-July/msg00115.html This also has links to earlier versions. v3: - The 01/11 patch in v2 included a bunch of unnecessary plus one necessary change to how input_password is passed around. I moved the necessary change into the final patch (implementing SSH password authentication) and dropped the rest. - The 01/11

Originally posted here: https://www.redhat.com/archives/libguestfs/2019-April/thread.html#00054 https://www.redhat.com/archives/libguestfs/2019-April/msg00076.html https://www.redhat.com/archives/libguestfs/2019-April/msg00126.html This is a rebase on top of current master branch with no other changes. The first patch in the old series was pushed a while back, and the last "TEMPORARY"

v3 posted here: https://www.redhat.com/archives/libguestfs/2019-July/msg00200.html v4: - The first patch in the v3 series was just a trivial doc whitespace fix so I pushed it. - There's a new patch using the nbdkit-retry-filter. This is not actually upstream in nbdkit but we know enough about how it will work. - Rebased against master and reran the tests. Rich.

This patch is incomplete, but early feedback would be welcome. Rich.

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all