search for: hbs

Hi folks... check this out.. > GLU<-lme(gluc~rt*cd4+sex+age+rf+nadir+pharmac+factor(hcv)+factor(hbs)+ + haartd+hivdur+factor(arv), + random= ~rt|id, na.action=na.omit) > intervals(GLU)$fixed lower est. upper (Intercept) 67.3467070345 7.362307e+01 7.989944e+01 rt *0.0148050160* 6.249304e-02 1.101811e-01 cd4 -0.0032133...

HBS seeks a Research Associate to partner with a faculty member in the Marketing Unit on research initiatives related to consumer and firm choices in industries influenced by technology along with value created through social media technologies. Projects involve statistical programing and econometr...

...ight at all, instead behaves like if it was a hig order polynomial or something similar!!!! I attach the codes below, hoping someone can point me the mistake.... I sincerely express many thanks in advance ...... Federico Bonofiglio frame3<-data.frame(id,chol,cd4,rt,sex,age, nadir,pharmac2,hbs,hcv,resp2, hivbl,switch) # I run a model specifing the function (t-t*)+ = 0 if t<=t* AND (t-t*)+ = t if t>t* with the following syntax, emulating MJ Crawley (The R book 2007, Wiley), # rt+rt*(rt>15) I run the model, is a mixed effect one....... PCWISE<-lme(chol~rt+rt*(rt&...

Got a HBS (y'know, Honkin' Big Server, one o' them technical terms), a Dell 720 with two Tesla GPUs. I updated the o/s, 6.5, and I cannot get the GPUs recognized. As a last resort, I d/l NVidia's proprietary driver/installer, 325, and it builds fine... I've yum removed the kmod-nvidia I h...

...nd the command that tells it to create the device in /dev/mapper from the info in /etc/crypttab. Clues for the poor? Yes, the server will, at some point in the future, go to CentOS 7, but that needs my user to be off for a while, and his jobs run literally for weeks, with loads upwords of 30 on an HBS (honkin' big server).... mark

CentOS 6.6 I've got two servers, server1 and hbs (honkin' big server). Both are running munge, and torque... *separately*. My problem is that I've got users who want to be able to submit from server1 to hbs. I see that munged can be pointed to an alternate keyfile... but is there any way to tell qsub what to use? (And yes, I got on the t...

...ate the device in /dev/mapper from the info in /etc/crypttab. >> >> Clues for the poor? Yes, the server will, at some point in the future, >> go to CentOS 7, but that needs my user to be off for a while, and his jobs >> run literally for weeks, with loads upwords of 30 on an HBS (honkin' big >> server).... > > MAPDEVICE=/dev/sdxy ; cryptsetup luksOpen ${MAPDEVICE} luks-$(cryptsetup > luksUUID ${MAPDEVICE}) Something's not right. I did cryptsetup luksOpen /dev/sdb luks-$(cryptsetup luksUUID $(/dev/sdb)) --key-file /etc/crypt.pw It did want the passw...

hello list, testing the 2.18 release i got following core dump. Maybe Timo you can get a look at it. greetings dominik Core Dump: root at hbs-buko:/var/vmail/hbs-buko.info/dominik.breu# gdb /usr/lib/dovecot/imap core GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redi...

...m my side. > > > + hb = &pv_lock_hash[hash_align(hash)]; So one thing this does -- and one of the reasons I figured I should ditch the LFSR instead of fixing it -- is that you end up scanning each bucket HB_PER_LINE times. The 'fix' would be to LFSR on cachelines instead of HBs but then you're stuck with the 0-th cacheline. > > + BUG_ON(hash == init_hash); > > + } > > + > > +done: > > + return &hb->lock; > > +}

...it to create > the device in /dev/mapper from the info in /etc/crypttab. > > Clues for the poor? Yes, the server will, at some point in the future, go > to CentOS 7, but that needs my user to be off for a while, and his jobs > run literally for weeks, with loads upwords of 30 on an HBS (honkin' big > server).... MAPDEVICE=/dev/sdxy ; cryptsetup luksOpen ${MAPDEVICE} luks-$(cryptsetup luksUUID ${MAPDEVICE}) MAPDEVICE=/dev/sdxy ; mount /dev/mapper/luks-$(cryptsetup luksUUID ${MAPDEVICE}) /mnt -- LF

.../dev/mapper from the info in /etc/crypttab. >>> >>> Clues for the poor? Yes, the server will, at some point in the future, >>> go to CentOS 7, but that needs my user to be off for a while, and his jobs >>> run literally for weeks, with loads upwords of 30 on an HBS (honkin' big >>> server).... >> >> MAPDEVICE=/dev/sdxy ; cryptsetup luksOpen ${MAPDEVICE} luks-$(cryptsetup >> luksUUID ${MAPDEVICE}) > > Something's not right. I did > cryptsetup luksOpen /dev/sdb luks-$(cryptsetup luksUUID $(/dev/sdb)) > --key-file...

Hi dears, I do > CHOL<-lme(chol~rt*cd4+sex+age+rf+nadir+pharmac+factor(hcv)+factor(hbs)+ haartd+hivdur+factor(arv), random= ~rt|id, na.action=na.omit) ...runs sweet,..then ....try a multicomparisons approach for the categorical rf > summary(glht(CHOL, linfct=mcp(rf="Tukey"))) * Error in model.frame.default(object, data, xlev = xlev) : l'oggetto non è una matric...

...3 name into 7 char, which the utility demands: *exactly* seven chars, no more, no less. And unlike the Dell utility, which give you lots of warm fuzzies ("collecting data", "this is for this hardware, this is newer, do you want to update?"), this just does it. Fortunately, this HBS contains a backup ROM, just in case.... And a three-finger kill later, it's up. And I put the memory boards back in, so we'll see if the BIOS update fixed the memory problems (remember them? this song's about them).... mark

On Mon, Apr 06, 2015 at 10:55:44PM -0400, Waiman Long wrote: > +++ b/kernel/locking/qspinlock_paravirt.h > @@ -0,0 +1,321 @@ > +#ifndef _GEN_PV_LOCK_SLOWPATH > +#error "do not include this file" > +#endif > + > +/* > + * Implement paravirt qspinlocks; the general idea is to halt the vcpus instead > + * of spinning them. > + * > + * This relies on the

On Mon, Apr 06, 2015 at 10:55:44PM -0400, Waiman Long wrote: > +++ b/kernel/locking/qspinlock_paravirt.h > @@ -0,0 +1,321 @@ > +#ifndef _GEN_PV_LOCK_SLOWPATH > +#error "do not include this file" > +#endif > + > +/* > + * Implement paravirt qspinlocks; the general idea is to halt the vcpus instead > + * of spinning them. > + * > + * This relies on the

...expect_close = 1 error packet at smbd/trans2.c(1814) cmd=50 (SMBtrans2) NT_STATUS_NO_SUCH_FILE Transaction 94 of length 45 switch message SMBclose (pid 2942) conn 0x8f6b038 close directory fnum=4670 Transaction 95 of length 112 switch message SMBntcreateX (pid 2942) conn 0x8f6b038 unix_mode(Script.hbs) returning 0764 error packet at smbd/trans2.c(2629) cmd=162 (SMBntcreateX) NT_STATUS_OBJECT_NAME_NOT_FOUND Transaction 76 of length 102 switch message SMBtrans2 (pid 2939) conn 0x8f6b038 call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 1004 call_trans2qfilepathinfo: SMB_VFS_STAT of mcscan.vlt...

I've noticed that the max.col function with the default "random" option often gives unexpected results. For instance, in this test, it seems clear what the answer should be: > # second col should always be max > x1 = cbind(1:10, 2:11, -Inf) > > # this works fine > max.col(x1, "first") [1] 2 2 2 2 2 2 2 2 2 2 > > # this gives random answers >

I've noticed that the max.col function with the default "random" option often gives unexpected results. For instance, in this test, it seems clear what the answer should be: > # second col should always be max > x1 = cbind(1:10, 2:11, -Inf) > > # this works fine > max.col(x1, "first") [1] 2 2 2 2 2 2 2 2 2 2 > > # this gives random answers >