search for: disarray

Hi folks, I noticed that llvm.org currently hosts two instances of the doxygen API docs, [1] and [2]. Is that intentional or by accident? What's a bit vexing about this is that googling specific APIs always ends up on [2]. However, [2] hasn't been updated for a year now and [1] would be the correct hit. But /doxygen is Disallowed through robots.txt. Best, Philip [1]

...lized patches. It's a bug that your attempts to revert are not being more vocal about failing due to lack of support. For now, you'll have to do the revert by manual use of qemu-img and editing of a libvirt <domain> XML; more details can be found on this wiki page (still in a bit of disarray, so feel free to edit it for clarity according to what works for you): http://wiki.libvirt.org/page/I_created_an_external_snapshot%2C_but_libvirt_won%27t_let_me_delete_or_revert_to_it -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

...looking pretty sane. Though I was loosing out on my sanity ... ! Finally, enlightenment crossed my mind and here is the problem and the solution: The "fsck -y" (see above) had not been able to handle all the errors and made the journal unusable. This is why all rescue and booting ended in disarray: the corrupted journal made the partition look invalid as ext3, though it was not so bad. I only had to convert it to ext2, have it repair all the errors and finally recreate the journal; effectively reconvert it to ext3. It is been running ever since without problem. I am even pondering to conside...

...ctivated NFS client attribute caching, etc., etc. It turned out that my predecessor had done something 10 years ago that was arcane, inscrutable and kludgy in the .procmailrc file. This *purposefully* trashed the dotlock. Not knowing what it did when I took over (predecessor long gone, things in disarray), I left it in, because I worried that something would break if we removed it. We have perpetuated it in creation of all new accounts. This procmailrc stanza looks like this: ####### BEGIN SYS ADMIN ADDED LINES ####### ## !!!!!! Do not remove these lines !!!!!! ## They have been placed here by...

> That's odd, because we have supported --live since 1.0.5. Are you sure > you are running the right libvirtd version and not just reporting the > version of your virsh? You are right. I am running an old libvirtd but with a new virsh. It works now! Thank you so much! Xinyang -- Xinyang GE Department of Computer Science & Engineering The Pennsylvania State University

Hello, I have 2 network cards on my 2 of my computers that I am trying to transfer data on. The second network cards are specifically for transferring files between the two so I enabled jumble frames by setting the mtu to 9000. I seem to be able to connect between the two via ssh and other methods using this setting so I thought everything was working right until I tried rsync. I used the

Let me skip most of the CoC comments which I largely agree with, both in terms of the proposed CoC and the need for having one in first place. On Tue, Oct 13, 2015 at 09:38:57PM +0200, Joachim Durchholz via llvm-dev wrote: > Actually I'm not yet convinced that LLVM really needs a CoC. If people have > been reluctant to join, I'm really, really sure it's not due to lack of CoC

https://bugzilla.samba.org/show_bug.cgi?id=11572 Bug ID: 11572 Summary: rsync --debug doesn't work, and gives erroneous results when taken out Product: rsync Version: 3.1.2 Hardware: x64 OS: Linux Status: NEW Severity: major Priority: P5 Component: core