search for: xinfo

Displaying 9 results from an estimated 9 matches for "xinfo".

Did you mean: info
2006 Jul 14
1
FW: error..please help me
...d] INFO (SrvDaemon:285) Xend Daemon started [2006-07-06 12:25:35 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, ''Invalid argument'')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, ''Invalid argument'') [2006-07-06 12:25:35 xend] INFO (SrvDaemon:185) Xend exited with status 1. [2006-07-06 12:28:35 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-07-06 12:28:35 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, ''In...
2006 Jul 20
3
Xend failure while installing Xen from source
...d] INFO (SrvDaemon:285) Xend Daemon started [2006-07-20 17:53:06 xend] ERROR (SrvDaemon:299) Exception starting xend ((22, ''Invalid argument'')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 288, in run xinfo = xc.xeninfo() error: (22, ''Invalid argument'') [2006-07-20 17:53:06 xend] INFO (SrvDaemon:185) Xend exited with status 1. The uname --all run shows: Linux blueman3 2.6.16-1.2133_FC5xen0 #1 SMP Tue Jun 6 02:40:06 EDT 2006 i686 i686 i386 GNU/Linux I had been able to get xen runnin...
2007 Mar 21
5
Xend cann''t run?
I''ve installed a Fedora Core 5 2054 and Xen 3.0.4.1 on a Intel 945 mainboard with xen3.0 user manual, everything seemed fine then. After I rebooted and chosed to enter into xen kernel , I find xend doesn''t run . when I try to run manually by input: /etc/init.d/xend start there some dot(indicating time maybe) appeared, and then nothing happened, the xend jun didn''t get
2017 Jan 13
0
[PATCH 1/4] Do not override CFLAGS, as CFLAGS is a user flag.
...bug=false ;; - *) AC_MSG_ERROR(bad value ${enableval} for --enable-debug) ;; -esac],[debug=false]) -AM_CONDITIONAL(DEBUG, test "x$debug" = xtrue) +AX_CHECK_ENABLE_DEBUG +AM_CONDITIONAL([DEBUG], [test "x$ax_enable_debug" = "xyes" -o "x$ax_enable_debug" = "xinfo"]) AC_ARG_ENABLE(sse, AC_HELP_STRING([--disable-sse], [Disable passing of -msse2 to the compiler]), @@ -384,15 +378,6 @@ AC_DEFINE(FLAC__HAS_NASM) AH_TEMPLATE(FLAC__HAS_NASM, [define if you are compiling for x86 and have the NASM assembler]) fi -if test "x$debug" = xtrue; the...
2017 Jan 15
0
[PATCH 1/2] Do not override CFLAGS, as CFLAGS is a user flag.
...e ;; - no) debug=false ;; - *) AC_MSG_ERROR(bad value ${enableval} for --enable-debug) ;; -esac],[debug=false]) -AM_CONDITIONAL(DEBUG, test "x$debug" = xtrue) +AM_CONDITIONAL([DEBUG], [test "x${ax_enable_debug}" = "xyes" || test "x${ax_enable_debug}" = "xinfo"]) AC_ARG_ENABLE(sse, AC_HELP_STRING([--disable-sse], [Disable passing of -msse2 to the compiler]), @@ -390,14 +390,13 @@ AC_DEFINE(FLAC__HAS_NASM) AH_TEMPLATE(FLAC__HAS_NASM, [define if you are compiling for x86 and have the NASM assembler]) fi -if test "x$debug" = xtrue; th...
2017 Jan 15
4
Updated CFLAGS patches and make test compilation conditional
Hi Erik, I've found a middleground for the problem of setting default CFLAGS. I've gone back to setting them if {C,CXX,CPP,LD}FLAGS are unset at the onset of the configure script (i.e., the user hasn't specified anything) and then proceed to set them to the defaults as before. This has been suggested before: https://lists.gnu.org/archive/html/autoconf/2006-04/msg00022.html In
2017 Jan 13
9
Upstreaming Gentoo patches
Dear FLAC devs, I would like to get some of our patches merged into master. Most of them deal with adhering to GNU conventions, respectively not overriding flags/variables that are up to the user to set. For instance, honoring $(htmldir) is important, as we have installation paths for the documentation that differ from what is currently coded in the various Makefile.am's. Regards David
2003 Mar 23
12
Shorewall 1.4.1
This is a minor release of Shorewall. WARNING: This release introduces incompatibilities with prior releases. See http://www.shorewall.net/upgrade_issues.htm. Changes are: a) There is now a new NONE policy specifiable in /etc/shorewall/policy. This policy will cause Shorewall to assume that there will never be any traffic between the source and destination zones. b) Shorewall no longer
2005 Feb 01
4
Shorewall problem
I am getting the following message when Shorewall stops can anybody shed any light on this message and where I should be looking? Thanks root@bobshost:~# shorewall stop Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Stopping Shorewall...Processing /etc/shorewall/stop ... IP Forwarding Enabled