search for: delayed

Displaying 20 results from an estimated 14477 matches for "delayed".

2019 Mar 26
0
[PATCH nbdkit v4 06/15] delay: Allow block status (extents) requests to be separately delayed.
--- filters/delay/nbdkit-delay-filter.pod | 8 ++++++++ filters/delay/delay.c | 26 ++++++++++++++++++++++++++ 2 files changed, 34 insertions(+) diff --git a/filters/delay/nbdkit-delay-filter.pod b/filters/delay/nbdkit-delay-filter.pod index c2eb172..2e2ac74 100644 --- a/filters/delay/nbdkit-delay-filter.pod +++ b/filters/delay/nbdkit-delay-filter.pod @@ -11,6 +11,7 @@
2011 Oct 03
2
patch: Replace many usleep and some sleep calls with nanosleep
...nt (YMMV); */ ser_send_char(upsfd, APC_CMD_GRACEDOWN); - usleep(UPSDELAY); + delay.tv_sec = 0; delay.tv_nsec = UPSDELAY; + nanosleep(&delay, NULL); ser_flush_in(upsfd, IGNCHARS, nut_debug_level); return 0; @@ -880,7 +883,8 @@ static int sdcmd_K(int dummy) upsdebugx(1, "Issuing delayed poweroff"); ser_send_char(upsfd, APC_CMD_SHUTDOWN); - usleep(CMDLONGDELAY); + struct timespec delay = {CMDLONGDELS, CMDLONGDELNS}; + nanosleep(&delay, NULL); ser_send_char(upsfd, APC_CMD_SHUTDOWN); return sdok(); @@ -893,7 +897,8 @@ static int sdcmd_Z(int dummy) upsdebugx(1, &q...
2006 Apr 05
5
BUG: soft lockup detected on CPU#0!
BUG: soft lockup detected on CPU#0! Pid: 17178, comm: xvd 275 fd:86 EIP: 0061:[<c0133b65>] CPU: 1 EIP is at kthread_should_stop+0x15/0x20 EFLAGS: 00000246 Not tainted (2.6.16-xen0 #1) EAX: 00000001 EBX: 00000000 ECX: c05431b4 EDX: 00000000 ESI: 00000000 EDI: cc7b143c EBP: c5f11f98 DS: 007b ES: 007b CR0: 8005003b CR2: 090a8928 CR3: 0635f000 CR4: 00000660 [<c0387bd5>]
2014 Jan 22
2
NIC Throwing errors I dont understand
I am having an issue where eth1 is throwing some messages and stops responding. Restarting networking doesn't work and also just bringing down eth1 with 'ifdown' doesn't fix it. I have never seen anything like these messages: eth1: no IPv6 routers present r8169 0000:03:00.0: eth1: rtl_counters_cond == 1 (loop: 1000, delay: 10). r8169 0000:03:00.0: eth1: rtl_chipcmd_cond == 1
2015 Mar 11
0
nutdrv_atcl_usb
2015-03-11 14:21 GMT+01:00 Jakub Scepka <jakub.scepka at gmail.com>: > Would you be so kind and provide some examples (commands), please? > I would run them today in the evening and report back with the logs. First, be sure to have in upsd.users a valid entry to set vars and execute instant commands: [<username>] password = <password> actions = SET instcmds = ALL where
2008 May 13
1
deliver exits with status 89 on some but not all mails of a batch
Hi, I'm trying to get dovecot's LDA 'deliver' to deliver mails that come in through a postfix daemon on the same box. I'm talking about dovecot version 1.0.rc15 (on CentOS 5 as Linux-VServer guest on a CentOS 5 host). Configuration ------------- # /etc/dovecot.conf ssl_cert_file: /etc/pki/selfmade/server.crt ssl_key_file: /etc/pki/selfmade/server.key login_dir:
2019 Jul 26
1
[nbdkit PATCH] delay: Avoid numeric overflow
Attempting delay-read=1000 results in no delay whatsoever: 1000 seconds, scaled to milliseconds, stored in int, then subjected to .tv_nsec = (ms * 1000000) % 1000000000 results in .tv_nsec being set to 567587328 thanks to 32-bit overflow, but that in turn results in instant EINVAL failure of nanosleep(). Fix it by diagnosing failure to fit in an int during config, and avoid math that
2015 Mar 11
2
nutdrv_atcl_usb
Would you be so kind and provide some examples (commands), please? I would run them today in the evening and report back with the logs. Thank you. Jakub S. On Tue, Mar 10, 2015 at 11:44 PM, hyouko at gmail.com <hyouko at gmail.com> wrote: > mmh.. it looks like someone forgot to hit 'reply all'. > > - relaying the originally attached files (gzipped, minus the two >
2023 Nov 22
1
APC Modbus support is finally here!
Great! Thanks for the info, and hope the driver author can address the nits (forwarding now...) Jim On Wed, Nov 22, 2023, 15:05 d tbsky <tbskyd at gmail.com> wrote: > Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > > > Got an update for APC Modbus users: a new PR is waiting for real-life > testing for settable variables and instant commands
2023 Nov 22
1
APC Modbus support is finally here!
Great! Thanks for the info, and hope the driver author can address the nits (forwarding now...) Jim On Wed, Nov 22, 2023, 15:05 d tbsky <tbskyd at gmail.com> wrote: > Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > > > Got an update for APC Modbus users: a new PR is waiting for real-life > testing for settable variables and instant commands
2023 Nov 24
1
APC Modbus support is finally here!
I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Thanks in advance, Jim Klimov On Wed, Nov 22, 2023 at 3:20?PM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Great! Thanks for the info, and hope the driver author can address the > nits (forwarding now...) > > Jim
2023 Nov 24
1
APC Modbus support is finally here!
I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Thanks in advance, Jim Klimov On Wed, Nov 22, 2023 at 3:20?PM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Great! Thanks for the info, and hope the driver author can address the > nits (forwarding now...) > > Jim
2018 Jan 17
0
[PATCH 9/9] filters: Move rdelay/wdelay from file plugin to new delay filter.
Previously the file plugin supported ‘rdelay’ and ‘wdelay’ parameters for injecting delays (for testing) into read and write requests. This moves the functionality to a new delay filter so that it can be used with any plugin. --- TODO | 3 - configure.ac | 1 + filters/Makefile.am | 1 + filters/delay/Makefile.am
2023 Nov 22
1
APC Modbus support is finally here!
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. > > https://github.com/networkupstools/nut/pull/2184 > > As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and
2023 Nov 22
1
APC Modbus support is finally here!
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. > > https://github.com/networkupstools/nut/pull/2184 > > As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and
2023 Nov 18
1
APC Modbus support is finally here!
Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov
2023 Nov 18
1
APC Modbus support is finally here!
Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. https://github.com/networkupstools/nut/pull/2184 As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and TCP may already be well served by a distro near you! Jim On Sun, Oct 22, 2023, 01:08 Jim Klimov
2009 Jun 30
3
Delays estimation in Speex algorithms
Speex tells me that the decoder is always 5 ms, but it says that the encoder is 5 ms for NB, 8.9375 ms for WB, and 10.90625 ms for UWB. Is there an extra frame of delay in the encoder that isn't otherwise accounted for? John Ridges Jean-Marc Valin wrote: > Quoting John Ridges <jridges at masque.com>: > >> I also need to know the precise delays from Speex but I used
2007 Jan 27
2
Meaning of ups.delay.*
Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?
2007 Jan 27
2
Meaning of ups.delay.*
Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?