search for: fsets

Hi, A system running ext3 crashed this afternoon (nothing to do with ext3, bad network driver). Is was saving a file from emacs when it happened. The file system is 0.06b and had ordered data as the mount option. Let me emphasize this was running ext3 pure, not with SnapFS or InterMezzo layered on top of it. strace reveals that Emacs does open("existing file name", O_TRUNC |

Dear R developers, when running R CMD check, the R Under development (unstable) (2015-01-13 r67453) gives me the following NOTE: cbind.fsets: possible error in list(...): ... used in a situation where it does not exist The file that causes this note contains: cbind.fsets <- function(..., deparse.level = 1) { dots <- list(...) res <- NULL resVars <- NULL resSpecs <- NULL for (i in seq_along(dots))...

Hi all This one has me baffled - leading me to beleive it could be a bug similar to https://bugzilla.samba.org/show_bug.cgi?id=2695 I am running samba 3.0.20b on debian unstable and am having problems with some users not resolving properly using winbind. wbinfo -u shows all users on the system, no problem wbinfo -a user%password works for any user getent passwd shows most but not all users

If I run cvec<-c("test.f", "test.sf", "try.g","try.res", "try.f") print(cvec) indx<-grep('\.f',cvec,perl=TRUE) fset<-cvec[indx] print(fset) I get > cvec<-c("test.f", "test.sf", "try.g","try.res", "try.f") > print(cvec) [1] "test.f" "test.sf"

...ssages are not terribly explanatory) Hadley On Wed, Jan 14, 2015 at 1:42 AM, Michal Burda <michal.burda at osu.cz> wrote: > Dear R developers, > > when running R CMD check, the R Under development (unstable) > (2015-01-13 r67453) gives me the following NOTE: > > > cbind.fsets: possible error in list(...): ... used in a situation > where it does not exist > > > The file that causes this note contains: > > > cbind.fsets <- function(..., deparse.level = 1) { > dots <- list(...) > > res <- NULL > resVars <- NULL >...

On 02/14/2012 11:01 AM, Jun Koi wrote: > On Tue, Feb 14, 2012 at 11:47 PM, Alex Jia <ajia at redhat.com> wrote: >> Hi Jun, >> I assume you haven't changed libvirt default URI, it may be a issue, >> I want to know whether it works for you if you explicitly specify >> --connect qemu:///system with virt-install? I think a root reason >> probably is your disk

Hello out there, my first try to install a package (e.g. ctest from CRAN) didn't succeed; looking at the error messages I think it must be a configuration problem of my machine, but as I'm not very experienced I would be glad if someone could give me a hint ... R's version is 0.63.0, my i386-Linux is kernel 2.0.35. I hadn't had problems to compile R, and R itself seems to work.

...$key =3D shift;=0A my $value =3D shi= ft;=0A $config{$key} =3D $value;=0A}=0A=0Asub config_complete=0A{=0A = die "no file=3D... parameter given" unless exists $config{file};=0A=0A m= y $file =3D $config{file};=0A $estimated_size =3D 0;=0A=0A # Parse th= e XVA file for offsets.=0A # XXX Does not work if the XVA contains multi= ple disk images. We=0A # should parse the 'Ref:NN' field too.=0A ope= n FILE, "tar tRvf $file |" or die "$file: $!";=0A while (<FILE>) {=0A = if (m{^block (\d+): \S+ \d+/\d+\s+(\d+)\s.*/0*(\d+)$...

Hello, We are using CTDB / Samba to serve a number of windows users, at this point around 1200. We have a 4 node CTDB setup. CTDB version - ctdb-1.0.114.7-1 Samba Version - sernet-samba-4.1.16-10 In recent months we've seen a big problem when 1 of the CTDB nodes is stopped or disconnected either manually or resulting from a problem. On some occasions, all other nodes get banned if a node

Package: xen-utils-4.0 Version: 4.0.1-2 If you reboot with the DomU disk DRBD domain destroy. pygrub error when trying to run a image on DRBD device My config DomU ------------------------------------------------------ bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '256' cpus="8-15" root = '/dev/xvda2 ro' #disk

2017-11-15 21:29 GMT+01:00 Richard W.M. Jones <rjones@redhat.com>: > Gandalf, is there an XVA file publically available (pref. not > too big) that we can look at? I can try to provide one, but it's simple: # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 ---------- 0/0 42353 1970-01-01 01:00 ova.xml ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000