search for: msg00110

Guys, We''re having a similar problem to that documented, but not resolved, here: http://lists.xensource.com/archives/html/xen-users/2005-08/msg00110.html The python process that runs "/usr/sbin/xend start" has reached 99.9% CPU utilization. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3569 root 25 0 12952 7876 2456 R 99.9 6.2 13444:26 python /usr/sbin/xend start xm commands don''t respond,...

...digging, I discovered that my registry was littered with connection bindings for all the previous install/uninstall's i'd done with the TAP Driver. Cleaning up this mess fixed the problem and tinc was running again. Google found this report http://osdir.com/ml/network.openvpn.user/2003-12/msg00110.html While this report suggests that the issue has been fixed in XP, my recent experience suggests otherwise? Doing an uninstall of the TAP Driver does not remove the registry bindings. A reboot makes no difference. Appears to be a Windows problem as uninstalling some other virtual driver resul...

As I shared on this forum last week, I did a bad boo boo when I erased my /boot/ directory without a backup - all of the things I caution other NOT to do. Nevertheless, after trying to put things back in order, today I decided to try a reboot and I get a GRUB prompt. Next I have put my Linux 4 disk in the CD drive and have selected the "linux repair" mode which has put me into the

...emp then put How so you set this up? In the environment? Usually, you include something like BuildRoot: /home/me/X/RPM/temp in the spec file, and "rpmbuild" sets up the variable for you during build. You can also use %{buildroot}. See https://www.redhat.com/archives/rpm-list/2002-July/msg00110.html. These days you generally get a usable build root without specifying anything. "%{...}" represents the expansion of a so-called rpm macro - it's the rpm macro equivalent to the shell's "${...}". rpmbuild defines a number of macros for you automatically and/or re...

Im trying to learn how to create RPMs but am a little confused by the spec file. Im trying to package up some Python scripts, rather than binary files, and I want them to be installed in a subdirectory under /usr/local which I shall refer to as /usr/local/X Ive put the scripts in a tarball under /home/me/X/RPM/SOURCES but Im getting terribly confused over what to put in the? %build %install

On 5/2/2014 11:41 PM, David Blaikie wrote: > Any idea what all those sections are - comdat inline functions? > No idea, as I cannot run objdump -h on a object file that I couldn't build :) Anyhow, I have an old, successful Debug+Asserts build of clang, made with Mingw also, for clang revision 206070. Apparently, the ASTContext.o file there contained 16453 sections, not 33066, as