search for: irrepar

Betr. Debian SID /64 BIT IA32-Apt-get install is a very bad idea The System will be irreparably damaged New installation is announced Bulid-Dep New Versions apt-get build-dep wine-unstable ! Sorry Google Translation Thank You

...splays some sort of error message. Looks like this: > x11() > library(tcltk) Loading Tcl/Tk interface ... > Now you can type additional commands in, at your peril! For example, if I type in the text "library", nothing happens, but "library(" causes R to freeze up irreparably, with "executing: try(gsub('\\s+','',paste(capture.output(print(args(library)))),collapse=")),silent=TRUE)" displayed at the bottom. When this happens, there's nothing you can do but restart R because it's completely frozen. I'm running R version 2.1...

Il 15-03-2018 09:13 Ján Tomko ha scritto: > It is not safe. > > For a running domain, you need to go through libvirt and also save the > memory of the VM - doing just the disk snapshot for a running machine > would be an equivalent of copying a physical hard drive after pulling > out the power cord. > > Jan Hi Jan, I 100% agree that taking a snapshot without dumping the

Hello, I'm about to migrate a number of existing users who have been using POP3 with emails stored locally in KMail's Maildir format into an IMAP solution based on Dovecot. Will it be possible to simply move all the KDE Maildir folders from the local PCs to the Maildir folder on the IMAP server running Dovecot and then have the emails accessible on the server, or will this most likely

Hi all, I would like to propose an improvement of the “almost dead” block elimination in Transforms/Local.cpp so that it will preserve the canonical loop form for loops with a volatile iteration variable. *** Problem statement Nested loops in LCALS Subset B (https://codesign.llnl.gov/LCALS.php) are not vectorized with LLVM -O3 because the LLVM loop vectorizer fails the test whether the loop

...disk have a chance to > corrupt the *original* disk Qcow2 image file? Yes, having two processes (in this case, the qemu process under libvirt's control, and the qemu-img process) both trying to write to a single qcow2 file at once is a recipe for disaster. You are VERY likely to cause irreparable disk corruption; although at least newer qemu/qemu-io binaries now use file locking to at least fail up front when they detect that another process has the image open for writing, rather than letting you shoot yourself in the foot. The only SAFE way to take a snapshot of a running virtual m...

Hi. I guess the world is full of these, one more won't hurt: "The ogg-cdparanoia script is a wrapper of the programs cdparanoia (http://www.xiph.org/paranoia/), sox (http://sox.sourceforge.net/) and oggenc (http://www.vorbis.com/). The process is simple: for each track, cdparanoia is called to extract the audio to a temporary wav file. Sox is used on it to see if it is normalized.

Guys, I have a up and running Samba4 as an AD DC, along side with 3 Domain Controllers, like like: 1- Master - ubuntu-ad-1.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 2- Slave - ubuntu-ad-2.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 3- Slave - ubuntu-ad-3.sambadom.company.com - Ubuntu Trusty + Samba 4.1.11 + Bind9 4- Slave - pdwad-1.sambadom.company.com -

...TheLoop->getLoopLatch()) { ... -Hal > That seems both counter-intuitive and unlikely to be a useful goal. > We simply don't optimize volatile operations well in *any* part of > the optimizer, and I'm not sure why we need to start trying to fix > that. This seems like an irreparably broken benchmark, but perhaps > there is a motivation I don't yet see. > Assuming that sufficient motivation arises to try to fix this, see my > comments below: > > (1) Loop unswitching generates several empty placeholder BBs only > > with PHI nodes after separating o...

Hi, I''m still seeing a very strange issue here. First, let''s clarify that the issue has never occurred with the good old xen 3.x and the good old 2.6.18 kernel. So the issue is, that with xen 4.x (including 4.1.1) pretty much any kernel (including kernel from [1] and vanilla 3.0.0, didn''t test the 2.6.18), the machine freezes during a reboot. The machine won''t

Hello, It's me again with one more misunderstanding of libguestfs usage... Guestfish (as well as python libguestfs module) refuse to mount logical volume containing the root partition of the VM's filesystem. According to this short guide<http://rwmj.wordpress.com/2009/04/07/libguestfs-lvm-support/> I am trying to mount /dev/vg_kojit/lv_root as "/", but nothing works:

I'm sure this is a stupid question, but I'm not finding an answer anywhere. Do I need a dedicated box to run asterisk, or can I put in my server (running Fedora) and leverage some of the free cpu cycles and disk space? Thanks, Dunc

...ntuitive and unlikely to be a useful > > > goal. > > > We simply don't optimize volatile operations well in *any* part > > > of > > > the optimizer, and I'm not sure why we need to start trying to > > > fix > > > that. This seems like an irreparably broken benchmark, but > > > perhaps > > > there is a motivation I don't yet see. > > > > > > Assuming that sufficient motivation arises to try to fix this, > > > see > > > my > > > comments below: > > > > >...

...> Because i think you db is corrected and beyond recovery. No, I do not have that backup mechanism implemented, and from reading that wiki page's notes about backing up live databases I have come to the conclusion that CrashPlan backed up /var/lib/samba/ while the databases were live and irreparably damaged them. I don't know what the relationship between /var/lib/samba/ and /var/cache/samba/ is exactly, but I assume that any backup I had created via CrashPlan (if it had worked instead of wreaking havoc) probably wouldn't have been valid lacking the /var/cache/samba/ directory con...

...hink you db is corrected and beyond recovery. > No, I do not have that backup mechanism implemented, and from reading that > wiki page's notes about backing up live databases I have come to the > conclusion that CrashPlan backed up /var/lib/samba/ while the databases were > live and irreparably damaged them. I don't know what the relationship > between /var/lib/samba/ and /var/cache/samba/ is exactly, but I assume that > any backup I had created via CrashPlan (if it had worked instead of wreaking > havoc) probably wouldn't have been valid lacking the /var/cache/samba...

...ft-key depressed, press the Y-key. You should get the response message SM. When you get the response message SM, Powerchute Plus can communicate with this connection. Warning: Do not enter any other characters via Hyperterminal other than that described in these instructions because this can cause irreparable damage to the UPS!! 7. Enter ?1? twice with a gap of two seconds. 8. The response message ?PROG? appears in the Hyperterminal window. 9. Enter a ?0? and the UPS reports the present value of the battery constant. In case this value does not correspond to the default value mentioned below, it...

Hello - I'm not sure if this is the right place to ask, so if not I will be grateful to learn of a more appropriate mailing list. I have a Slackware box (2.6.26 kernel) running Samba 3.0.25b (yes, I know, I'll upgrade soon). This machine provides DC functionality for several Windows XP workstations in my house. I recently changed the backend password database to OpenLDAP (v2.3.33)

<=?windows-1252?Q?L.P.H._van_Belle?=> writes: > > Hai, > > Can be incorrect rights, of corrupted db. > > Can you give the output of > > ls -al /var/lib/samba/ > ls -al /var/lib/samba/private > ls -al /var/lib/samba/private/dns > > Greetz, > > Louis > Hi Louis, thanks for your reply, here is the info you requested: ls -al

...;t optimize volatile operations well in *any* > > > > > part > > > > > of > > > > > the optimizer, and I'm not sure why we need to start trying > > > > > to > > > > > fix > > > > > that. This seems like an irreparably broken benchmark, but > > > > > perhaps > > > > > there is a motivation I don't yet see. > > > > > > > > > > > > > > > Assuming that sufficient motivation arises to try to fix > > > > > this, >...

...e is another strategy? > > -Hal > > That seems both counter-intuitive and unlikely to be a useful goal. > We simply don't optimize volatile operations well in *any* part of > the optimizer, and I'm not sure why we need to start trying to fix > that. This seems like an irreparably broken benchmark, but perhaps > there is a motivation I don't yet see. Assuming that sufficient > motivation arises to try to fix this, see my comments below: > > (1) Loop unswitching generates several empty placeholder BBs only > with PHI nodes after separating out a shorte...