search for: 160s

Estimados, tengo el siguiente problema: estoy trabajando con un data.frame que tiene 892 filas y 9 columnas, el cual adjunto para que puedan probar. Cuando consulto por las filas que cumplen una cierta condicion, por ejemplo, ... graph[graph$NCar==c("160s"),] obtengo el siguiente conjunto de datos: sol con dia NCar NIns isom area rep tipo 1 con 0.001 1 160s 0 s 0.6083543 1 8 con 0.001 2 160s 0 s 0.6388484 1 <NA> 10 con 0.001 3 160s 0 s 0.6873404 1 <NA> 13 con 0.001 4 160s 0 s...

...siguiente problema: estoy trabajando con un >> data.frame que tiene 892 filas y 9 columnas, el cual adjunto para que >> puedan probar. >> >> Cuando consulto por las filas que cumplen una cierta condicion, por >> ejemplo, ... >> >> graph[graph$NCar==c("160s"),] >> >> obtengo el siguiente conjunto de datos: >> >> sol con dia NCar NIns isom area rep tipo >> 1 con 0.001 1 160s 0 s 0.6083543 1 >> 8 con 0.001 2 160s 0 s 0.6388484 1 <NA> >> 10 con 0.001 3 160s 0...

Muchas gracias por la explicación Isidro! El 10 de septiembre de 2013 08:19, Isidro Hidalgo <ihidalgo@jccm.es>escribió: > Cuando utilizas "==" estás comparando el vector "graph$NCar" (longitud 892) > con otro de longitud 2: c("160s","180s"). > Es decir, comparas el primer valor de "graph$NCar" con el primer valor de > c("160s","180s"), el segundo valor de "graph$NCar" con el segundo valor de > c("160s","180s"), el tercer valor de "graph$N...

...ió: > Estimados, tengo el siguiente problema: estoy trabajando con un > data.frame que tiene 892 filas y 9 columnas, el cual adjunto para que > puedan probar. > > Cuando consulto por las filas que cumplen una cierta condicion, por > ejemplo, ... > > graph[graph$NCar==c("160s"),] > > obtengo el siguiente conjunto de datos: > > sol con dia NCar NIns isom area rep tipo > 1 con 0.001 1 160s 0 s 0.6083543 1 > 8 con 0.001 2 160s 0 s 0.6388484 1 <NA> > 10 con 0.001 3 160s 0 s 0.6873404 1 <NA>...

Cuando utilizas "==" estás comparando el vector "graph$NCar" (longitud 892) con otro de longitud 2: c("160s","180s"). Es decir, comparas el primer valor de "graph$NCar" con el primer valor de c("160s","180s"), el segundo valor de "graph$NCar" con el segundo valor de c("160s","180s"), el tercer valor de "graph$NCar" con e...

Estimada comunidad, tengo el siguiente problema: Un data.frame con muchas filas de las que debo eliminar aquellas que cumplen varios criterios al mismo tiempo. Por ejemplo este data.frame: sol con dia NCar NIns isom area rep tipo 1 con 0.001 1 160s 0 s 6.083543e-01 1 2 con 0.001 1 161c 1 c 1.391274e-03 1 <NA> 3 con 0.001 1 161c 1 c 2.812804e-03 1 <NA> 4 con 0.001 1 180s 0 s 3.791027e-01 1 <NA> 619 lim 0.003 2 160s 0 s 5.723237e-01 1 <NA> 620 lim 0.003 2 161t 1...

...ya columna SOL dice LIM y cuya columna >> DIA dice 2. >> > > ​​Prueba con: > > >library(sqldf)​​ > >graph<-sqldf("select * from graph where sol='lim' and dia=2") > > ​ sol con dia NCar NIns isom area rep tipo > 1 lim 0.003 2 160s 0 s 0.572323700 1 <NA> > 2 lim 0.003 2 161t 1 t 0.010960770 1 <NA> > 3 lim 0.003 2 161c 1 c 0.003896926 1 <NA> > 4 lim 0.003 2 190s 0 s 0.013402530 1 <NA> > 5 lim 0.003 2 190s 0 s 0.009274320 1 <NA> > ​ &gt...

...9;access=w,vdev=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote s...

...9;access=w,vdev=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.588319] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remote s...

...202 xvda:<6>netfront: Initialising virtual ethernet driver. XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...<6>Uniform Multi-Platform E-IDE driver SCSI subsystem initialized st: Version 20080504, fixed bufsize 32768, s/g segs 256 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. Non-volatile memory driver v1...

...Hola.​ > Tengo que eliminar las filas cuya columna SOL dice LIM y cuya columna > DIA dice 2. > ​​Prueba con: >library(sqldf)​​ >graph<-sqldf("select * from graph where sol='lim' and dia=2") ​ sol con dia NCar NIns isom area rep tipo 1 lim 0.003 2 160s 0 s 0.572323700 1 <NA> 2 lim 0.003 2 161t 1 t 0.010960770 1 <NA> 3 lim 0.003 2 161c 1 c 0.003896926 1 <NA> 4 lim 0.003 2 190s 0 s 0.013402530 1 <NA> 5 lim 0.003 2 190s 0 s 0.009274320 1 <NA> ​ ​Saludos.​ -- «But Gwind...

...gt;> DIA dice 2. > >> > > > > Prueba con: > > > > >library(sqldf) > > >graph<-sqldf("select * from graph where sol='lim' and dia=2") > > > > sol con dia NCar NIns isom area rep tipo > > 1 lim 0.003 2 160s 0 s 0.572323700 1 <NA> > > 2 lim 0.003 2 161t 1 t 0.010960770 1 <NA> > > 3 lim 0.003 2 161c 1 c 0.003896926 1 <NA> > > 4 lim 0.003 2 190s 0 s 0.013402530 1 <NA> > > 5 lim 0.003 2 190s 0 s 0.009274320 1 &...

...ily 17 [ 0.976739] registered taskstats version 1 [ 6.077230] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 301.076163] XENBUS: Timeout connecting to device: device/vbd/2050 (local state 3, remote st...

...ading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3, remote state 1) Loading...

Hi all, I'm debugging a performance problem for a client. Needless to say, the organisation of their data is such that this problem is really annoying. Here's the situation: Samba 3.0.x PDC in a mixed 9x/nt/xp environment, using acls. When trying to delete a large number of folders from a folder, the 'preparing to delete' stage takes about half hour. It's simple to repeat:

I want to configure my zfs like this : concatination_stripe_pool : concatination lun0_controller0 lun1_controller0 concatination lun2_controller1 lun3_controller1 1. There is any option to implement it in ZFS? 2. there is other why to get the same configuration? thanks This message posted from opensolaris.org

...driver [ 0.260194] NET: Registered protocol family 17 [ 0.260213] Bridge firewalling registered [ 5.360075] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s... 205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s... 150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s... 95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s... 35s...30s...25s...20s...15s...10s...5s...0s... [ 270.360180] XENBUS: Timeout connecting to device: device/vbd/51713 (local state 3, remot...

Hi everyone, I'm looking into setting up a SATA hardware raid, probably 5 to use with CentOS 4. I chose hardware raid over software mostly because I like the fact that the raid is transparent to the OS. Does anyone know of any SATA controllers that are well tested for this sort of usage? From what I can tell from googling, this is more or less where RHEL stands: Red Hat Enterprise Linux