S
stefanopronti
Guest
Hello,
many thanks to the Proxmox staff for their work.
just two questions:
1)
I just upgraded one of my cluster nodes to 3.0 from 2.3 and found that web server API proxy does not activate redirection from ports 80 and 443 to 8006.
I am wondering if it is configurable and how, or if it is due to other reasons and which.
2)
after upgrade my server sent me an email like this:
eglibc (2.13-25) unstable; urgency=medium
Starting with the eglibc package version 2.13-5, the libraries are
shipped in the multiarch directory /lib/<triplet> instead of the more
traditional /lib, where <triplet> is the multiarch triplet and can be
retrieved with 'dpkg-architecture -qDEB_HOST_MULTIARCH'. Similarly the
includes are now shipped in /usr/include/<triplet> instead of the more
traditional /usr/include.
The toolchain in Debian has been updated to cope with that, and most
build systems should be unaffected. If you are using a non-Debian
toolchain to build your software and it is not able to cope with
multiarch, you might try to pass the following options to your
compiler:
-B/usr/lib/<triplet> -I/usr/include/<triplet>
Alternatively if the build system makes hard to pass the above options,
you might try to set the LIBRARY_PATH and CPATH environment variables:
LIBRARY_PATH=/usr/lib/<triplet>
CPATH=/usr/include/<triplet>
export LIBRARY_PATH CPATHshould I be worried?
should I do something?
--
many thanks for your reply,
Sorry for my poor english spaghetti-style.
Stefano
many thanks to the Proxmox staff for their work.
just two questions:
1)
I just upgraded one of my cluster nodes to 3.0 from 2.3 and found that web server API proxy does not activate redirection from ports 80 and 443 to 8006.
I am wondering if it is configurable and how, or if it is due to other reasons and which.
2)
after upgrade my server sent me an email like this:
eglibc (2.13-25) unstable; urgency=medium
Starting with the eglibc package version 2.13-5, the libraries are
shipped in the multiarch directory /lib/<triplet> instead of the more
traditional /lib, where <triplet> is the multiarch triplet and can be
retrieved with 'dpkg-architecture -qDEB_HOST_MULTIARCH'. Similarly the
includes are now shipped in /usr/include/<triplet> instead of the more
traditional /usr/include.
The toolchain in Debian has been updated to cope with that, and most
build systems should be unaffected. If you are using a non-Debian
toolchain to build your software and it is not able to cope with
multiarch, you might try to pass the following options to your
compiler:
-B/usr/lib/<triplet> -I/usr/include/<triplet>
Alternatively if the build system makes hard to pass the above options,
you might try to set the LIBRARY_PATH and CPATH environment variables:
LIBRARY_PATH=/usr/lib/<triplet>
CPATH=/usr/include/<triplet>
export LIBRARY_PATH CPATHshould I be worried?
should I do something?
--
many thanks for your reply,
Sorry for my poor english spaghetti-style.
Stefano