search for: 75s

...ehavior. y <- rnorm(1000) x <- seq(0, length=length(y)) plot(x, y, type='l', lty=1) - instantaneous plot(x, y, type='l', lty=2) - 18s plotting lines + 15s plotting axes = 33s plot(x, y, type='l', lty=3) - 76s ,, + 75s ,, = 151s plot(x, y, type='l', lty=4) - 40s ,, + 38s ,, = 78s A couple of observations: (1) The plots for lty>1 seem to be rendered in "one chunk", that is a blank graphics window appears and stays blank until all the lines a...

...o- disk = [''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 (lo...

...o- disk = [''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 (lo...

...ne I try to install a suse11 pv guest on redhat5.2 virtualization platform. But the startup process hung with messages: xen-vbd: registered block device major 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: Vers...

...aven't succeeded, which is why I'm asking. Here's the situation: I'm connect to a dual-stacked host with A and AAAA records. The IPv6 connectivity to the host is broken. When connecting to the host directly from my client system, the TCP connect to the IPv6 address times out after 75s, which is the TCP default timeout. After that, SSH proceeds to connect to the IPv4 address successfully. This causes a rather large delay. I can control this by setting "ConnectTimeout" to something lower, like 30s. So far, so good. However, when I'm not on a trusted network, I have...

...rtc_cmos: rtc core: registered rtc_cmos as rtc0 [ 0.976298] No iBFT detected. [ 0.976641] TCP cubic registered [ 0.976647] NET: Registered protocol family 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....

...ting block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading 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....

HI All, How fast does a a small DNS Server need to be? I will have about 10 servers and a few workstations. I have a few older Compaq PIII boxes with 1gb RAM each or I have faster P4 boxes. Same question as above, just a Vyatta type device, Firewalling....? -ML

...over IPv4 tunneling 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...

Hi, I''ve got a newbie question--sorry if this is covered elsewhere, I parsed through the archives for awhile and didn''t see it. I''d like to listen for whenever a file is renamed (e.g. foo.txt -> foo.old) and then magically change it back. This sounds odd, but I''m working with a stubborn application and this will actually make things work nice. So, if I do: