search for: 33s

...el: mfi0: 200251 (boot + 3s/0x0020/info) - Firmware version 1.40.342-1650 Sep 17 11:25:39 romulus kernel: mfi0: 200252 (boot + 4s/0x0008/info) - Battery Present Sep 17 11:25:39 romulus kernel: mfi0: 200253 (boot + 5s/0x0020/info) - Board Revision Sep 17 11:25:39 romulus kernel: mfi0: 200254 (boot + 33s/0x0010/info) - Connector External B Port (loc=3 sasMux=0x0) is active Sep 17 11:25:39 romulus kernel: mfi0: 200255 (boot + 33s/0x0010/info) - Connector Int.Ports 4-7 (loc=2 sasMux=0x1) is active Sep 17 11:25:39 romulus kernel: mfi0: 200256 (boot + 33s/0x0002/info) - Inserted: PD 1e(e0xff/s30) Sep 1...

Ok, So this is really more of an observation than anything else.? I had a FreeBSD 10.1 server that was running great. Some SSL issue came up, or I upgrade Dovecot in ports - something occurred and the machine started rebooting randomly.? It would run for 2 weeks, then reboot.? It might run for 5 days and then reboot. So I started doing more FreeBSD upgrades, thinking it was a kernel issue. The

I just ran into this strange behavior. 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&quo...

...mplete an upgrade to 7.6), but it is 'stuck' while shutting down with 'A stop job is running for ...' - the counter initially gave a limit of '1min 30s' - but each time it reaches that limit, it just adds on ~90 seconds to the limit ... Currently the limit is '25min 33s' I'm in no hurry to have this workstation operational, but I guess at some point I will have to power cycle it ... Does anyone know how to bypass this? - or at least stop it increasing the limit each time it is reached? It does seems rather pointless to keep increasing the limit like t...

...39; while shutting down with 'A stop >> job is running for ...' - the counter initially gave a limit of '1min >> 30s' - >> but each time it reaches that limit, it just adds on ~90 seconds to the >> limit ... >> >> Currently the limit is '25min 33s' >> >> >> I'm in no hurry to have this workstation operational, but I guess at >> some point I will have to power cycle it ... >> >> Does anyone know how to bypass this? - or at least stop it increasing >> the limit each time it is reached? >>...

...I try to start my AMaViS (A Mail Virus Scanner) amavisd.service - Amavisd-new is an interface between MTA and content checkers. Loaded: loaded (/usr/lib/systemd/system/amavisd.service; disabled; vendor preset: disabled) Active: failed (Result: start-limit) since Tue 2018-03-06 17:01:19 WAT; 33s ago Docs: http://www.ijs.si/software/amavisd/#doc Process: 11042 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=255) Mar 06 17:01:19 ERPServer systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers.. Mar 06 17:01:19 ERPServer...

...q_on=1 in combination with plugins like vddk, which has no overhead for returning information for multiple extents in one call, but that call is very time-consuming. Quick test showed that on a fast connection and a sparsely allocated 16G disk with a OS installed `qemu-img map` runs 16s instead of 33s (out of which it takes 5s to the first extents request). For 100G disk with no data on it, that is one hole extent spanning the whole disk (where there is no space for improvement) this does not add any noticeable overhead. Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- v2: - E...

..._one=1 in combination with plugins like vddk, which has no overhead for returning information for multiple extents in one call, but that call is very time-consuming. Quick test showed that on a fast connection and a sparsely allocated 16G disk with a OS installed `qemu-img map` runs 16s instead of 33s (out of which it takes 5s to the first extents request). For 100G disk with no data on it, that is one hole extent spanning the whole disk (where there is no space for improvement) this does not add any noticeable overhead. Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- Notes:...

...q_on=1 in combination with plugins like vddk, which has no overhead for returning information for multiple extents in one call, but that call is very time-consuming. Quick test showed that on a fast connection and a sparsely allocated 16G disk with a OS installed `qemu-img map` runs 16s instead of 33s (out of which it takes 5s to the first extents request). For 100G disk with no data on it, that is one hole extent spanning the whole disk (where there is no space for improvement) this does not add any noticeable overhead. Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- Yes, I h...

...h plugins like > vddk, which has no overhead for returning information for multiple extents in > one call, but that call is very time-consuming. > > Quick test showed that on a fast connection and a sparsely allocated 16G disk > with a OS installed `qemu-img map` runs 16s instead of 33s (out of which it > takes 5s to the first extents request). For 100G disk with no data on it, that > is one hole extent spanning the whole disk (where there is no space for > improvement) this does not add any noticeable overhead. > > Signed-off-by: Martin Kletzander <mkletzan@re...

...h plugins > like vddk, which has no overhead for returning information for multiple extents > in one call, but that call is very time-consuming. > > Quick test showed that on a fast connection and a sparsely allocated 16G disk > with a OS installed `qemu-img map` runs 16s instead of 33s (out of which it > takes 5s to the first extents request). For 100G disk with no data on it, that > is one hole extent spanning the whole disk (where there is no space for > improvement) this does not add any noticeable overhead. > > Signed-off-by: Martin Kletzander <mkletzan@re...

...7.6), but it is 'stuck' while shutting down with 'A stop job > is running for ...' - the counter initially gave a limit of '1min 30s' - > but each time it reaches that limit, it just adds on ~90 seconds to the > limit ... > > Currently the limit is '25min 33s' > > I'm in no hurry to have this workstation operational, but I guess at > some point I will have to power cycle it ... > > Does anyone know how to bypass this? - or at least stop it increasing > the limit each time it is reached? > > It does seems rather pointle...

Hi, Can some one tell me what is the meaning of all the fields of show queue callcenter? for example in my system it gives: callcenter has 0 calls (max unlimited) in 'roundrobin' strategy (33s holdtime), C:429, A:12, SL:0.0% within 0s How is the holdtime calculated? what is A and SL? Also how can I see which of my zap interfaces are busy currently? I did a zap show channels I get this output, but no indication as to which is busy and which is free. rapid*CLI> zap show channels...

...m Estimated Hours: 0.0 *When we use ranges in 'expiration' parameter. Nft doesn't show this range correctly. Here an example: $ sudo nft add rule ip test input ct expiration 33-50 $ sudo nft list table ip test table ip test { chain input { ct expiration >= "33s" ct expiration <= "9709d53m20s" -- Configure bugmail: https://bugzilla.netfilter.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

...ke s/on/one/ > vddk, which has no overhead for returning information for multiple extents in > one call, but that call is very time-consuming. > > Quick test showed that on a fast connection and a sparsely allocated 16G disk > with a OS installed `qemu-img map` runs 16s instead of 33s (out of which it > takes 5s to the first extents request). For 100G disk with no data on it, that > is one hole extent spanning the whole disk (where there is no space for > improvement) this does not add any noticeable overhead. > > Signed-off-by: Martin Kletzander <mkletzan@re...

...h plugins like > vddk, which has no overhead for returning information for multiple extents in > one call, but that call is very time-consuming. > > Quick test showed that on a fast connection and a sparsely allocated 16G disk > with a OS installed `qemu-img map` runs 16s instead of 33s (out of which it > takes 5s to the first extents request). For 100G disk with no data on it, that > is one hole extent spanning the whole disk (where there is no space for > improvement) this does not add any noticeable overhead. > > Signed-off-by: Martin Kletzander <mkletzan@re...

...w stack -- Executing Dial("Local/223@agents-f0ec,2", "SIP/223|24|rt") in new stack -- Called 223 -- Agent/223 is ringing -- SIP/235-8429 is ringing -- SIP/223-cc03 is ringing show queues commercial has 0 calls (max unlimited) in 'ringall' strategy (33s holdtime), C:7, A:0, SL:0.0% within 0s Members: Agent/223 has taken 1 calls (last was 6392 secs ago) Agent/235 with penalty 1 has taken no calls yet No Callers support has 0 calls (max unlimited) in 'ringall' strategy (21s holdtime), C:14, A:1, SL:0.0% within 0s M...

...G: soft lockup - CPU#5 stuck for 22s! [6_scheduler:64928] Message from syslogd at amer at Jan 27 19:31:25 ... kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:34] Message from syslogd at amer at Jan 27 19:32:42 ... kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 33s! [swift-object-up:11358] Message from syslogd at amer at Jan 27 19:33:55 ... kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 24s! [dmeventd:71548] Message from syslogd at amer at Jan 27 19:34:25 ... kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 65s! [kworker/2:0:59993] Messag...

...h plugins > like vddk, which has no overhead for returning information for multiple extents > in one call, but that call is very time-consuming. > > Quick test showed that on a fast connection and a sparsely allocated 16G disk > with a OS installed `qemu-img map` runs 16s instead of 33s (out of which it > takes 5s to the first extents request). For 100G disk with no data on it, that > is one hole extent spanning the whole disk (where there is no space for > improvement) this does not add any noticeable overhead. > > Signed-off-by: Martin Kletzander <mkletzan@re...

...opts[''extratime''] = v + elif k in [''-w'', ''--weight'']: + opts[''weight''] = v + + # print header if we aren''t setting any parameters + if len(opts.keys()) == 0: + print ''%-33s %-8s %-13s %-10s %-8s %-10s %-6s'' %(''Name'',''ID'',''Period'', + ''Slice'', ''Latency'', + '&...