Displaying 20 results from an estimated 13319 matches for "timeoutable".
Did you mean:
timeouttable
2018 Jan 22
3
What does this mean? select(1, [0], , NULL, {60, 0}) = 0 (Timeout)
I have been having broken pipe messages for a while. I think since a
network architecture change. But I am not sure because I have not been
monitoring the errors closely before. I added this
(https://rsync.samba.org/issues.html) rsync-debug.sh script with strace
of 100. But I have no idea how to interper this output.
I guess between 00:55:41 and 03:06:47 nothing is happening? And then
some
2018 Jan 22
0
What does this mean? select(1, [0], , NULL, {60, 0}) = 0 (Timeout)
From man 2 select:
int select(int nfds, fd_set *readfds, fd_set *writefds,
fd_set *exceptfds, struct timeval *timeout);
So, it is waiting for file descriptor #1 to become available with a 60
second timeout which it is hitting.
Use lsof to find out what file descriptor #1 is.
On 01/22/2018 10:07 AM, Marc Roos via rsync wrote:
>
> I have been having broken pipe messages for a while. I
2018 Nov 29
1
[Bug 108906] New: nouveau driver causes system slowdown
https://bugs.freedesktop.org/show_bug.cgi?id=108906
Bug ID: 108906
Summary: nouveau driver causes system slowdown
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee:
2019 Jan 02
3
[lit] check-all hanging
Hi,
>From time to time, I see check-all hang during running of lit tests.
The hang always happens at the > 90% completion stage and I'm pretty
sure all tests have been run and check-all is just waiting for
lit/python to exit. I see a single python processing running, taking
very little CPU time. An strace of that process shows this:
select(0, NULL, NULL, NULL, {0, 50000}) = 0
2005 Aug 09
0
Random Zap Channel Resets
Every so often, and it seems that it happens only when a call is in
progress, all 24 Zap channels get reset. All channels are opened and then
timeout. This causes the in-progress calls to terminate.
There are no corresponding Red/Yellow alarms on wither the PBX or Asterisk
although we do receive a fair amount of Blue Alarms.
The Asterisk server is connected to a legacy PBX through a Digium
2019 Jan 02
4
[lit] check-all hanging
Hi David, Chandler,
I see lldb tests hang often, and then I kill the dotest process.
I'd like to stop running check-all too, but I feel it's important when I
modify FileCheck. The flakiness that Chandler mentioned makes it
time-consuming to verify test results.
Joel
On Wed, Jan 2, 2019 at 4:41 PM Chandler Carruth via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> What
2019 Apr 26
2
faI2ban detecting and banning but nothing happens
On Saturday 20 April 2019 00:32:43 Pete Biggs wrote:
> What ban action do you use? If it's something like iptables-multiport,
> then I wonder if the fact that it's detecting the failures as
> '[dovecot]' means that it's using the dovecot ports, not the exim
> ports, when applying the iptable rule.
>
> When a host has been banned, can you look at the
2020 Aug 13
0
assert in nouveau_vp3_video_vp.c ?
here:
diff --git a/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c b/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c
index 53f5db0003d..efd9cf2b004 100644
--- a/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c
+++ b/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c
@@ -365,7 +365,7 @@ nouveau_vp3_fill_picparm_h264_vp(struct nouveau_vp3_decoder *dec,
refs[j] = (struct
2006 Dec 15
3
can Timeout::timeout(...) be used in a Worker ?
Hi ,
I was wondering if anyone else has tried to use the Timeout::timeout
method in a backgroundrb Worker and had Timeout raise an exception
after the allotted amount of time .
I ask because i have written a test script to make sure Timeout would
work . I have tested the script by directly feeding it to ruby with :
$ ruby test_script.rb
and piping the script to the rails console:
$
2015 Nov 14
3
[lit] RFC: Per test timeout
Hi,
A feature I've wanted in lit for a while is a having a timeout per
test. Attached
are patches that implement this idea.
I'm e-mailing llvm-dev rather than llvm-commits
because I want to gather more feedback on my initial implementation and
hopefully some answers to some unresolved issues with my implementation.
Currently in lit you can set a global timeout for
all of the tests but
2018 Apr 27
4
[PATCH] allow indefinite ForwardX11Timeout by setting it to 0
This change allows use of untrusted X11 forwarding (which is more
secure) without
requiring users to choose a finite timeout after which to refuse new
connections.
This matches the semantics of the X11 security extension itself, which
also treat a
validity timeout of 0 on an authentication cookie as indefinite.
Signed-off-by: Trixie Able <table at inventati.org>
---
clientloop.c | 12
2014 Jan 28
1
[PATCH] run: Actually use timeout --foreground option (RHBZ#1025269).
The following commit managed to not actually add the --foreground
option to the timeout command, just test for it. Add it this time.
commit 681488877456b83f039dc518861f29ab4e1857f0
Author: Richard W.M. Jones <rjones@redhat.com>
Date: Thu Dec 19 08:21:53 2013 +0000
run: Use timeout --foreground option.
If timeout doesn't have this option (RHEL 6) don't use timeout
2011 Nov 13
0
Major opcode of failed request: 93 (X_CreateCursor)
Hi,
I got selected for beta testing SW:TOR and managed to get the installer to work on wine but it keeps crashing when I try with the launcher. It opens for a smidgen then crashes. Here's all the script I get;
fixme:iphlpapi:NotifyAddrChange (Handle 0x32e604, overlapped 0x8f8d58): stub
fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
fixme:winsock:WSALookupServiceBeginW (0x32e628
2003 Jul 31
2
rsync 2.5.6 timeout bug
I've been getting frequent io errors trying to synchronise a local CPAN
mirror with the master on ftp.funet.fi, the symptoms being the dreaded
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165)
message at the client end. I've replicated this when mirroring from a local
CPAN mirror, and the issue seems to
2020 May 14
1
system(timeout=) may timeout with 0 exit code
Hi R developers,
I observed that system(timeout=) may still return exit code 0, when
killing the process due to timeout.
In src/unix/sys-unix.c there is
#define KILL_SIGNAL1 SIGINT
#define KILL_SIGNAL2 SIGTERM
#define KILL_SIGNAL3 SIGKILL
#define EMERGENCY_TIMEOUT 20
After little bit of debugging I observed that total time of system
call is provided timeout value + 20s. That means
2013 Dec 03
8
[Bug 880] New: ipset doesn't refresh the timeout for an existing entry when the table is FULL.
https://bugzilla.netfilter.org/show_bug.cgi?id=880
Summary: ipset doesn't refresh the timeout for an existing
entry when the table is FULL.
Product: ipset
Version: unspecified
Platform: x86_64
OS/Version: Fedora
Status: NEW
Severity: normal
Priority: P5
Component: default
2015 Nov 20
2
Contact-closure UPS
No progress has been made:
cable is UPS - PC
6 - 3
7 - 5
9 - 2
for ./blazer_ser -DDDDD -a infosec
0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1"
0.000323 debug level is '5'
0.103068 send_to_all: SETINFO device.type "ups"
0.103104 send_to_all: SETINFO driver.version "2.7.3"
0.103118 send_to_all: SETINFO
2016 Oct 01
2
socketSelect(..., timeout): non-integer timeouts in (0, 2) (?) equal infinite timeout on Linux - weird
There's something weird going on for certain non-integer values of
argument 'timeout' to base::socketSelect(). For such values, there is
no timeout and you effectively end up with an infinite timeout. I
can reproduce this on R 3.3.1 on Ubuntu 16.04 and RedHat 6.6, but not
on Windows (via Linux Wine).
# 1. In R master session
> con <- socketConnection('localhost', port
2009 Dec 15
1
--timeout not honoured
Hi
I already wrote about this problem half a year ago but didn't get
an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html
I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800.
But still I often have rsync stall much longer than that.
Some examples:
2009/12/14 23:14:35 [8707] io timeout after 11670 seconds -- exiting
2009/12/14 23:14:35 [8707]
2017 Oct 05
1
socketSelect(..., timeout): non-integer timeouts in (0, 2) (?) equal infinite timeout on Linux - weird
Fixed in 73470
Best,
Tomas
On 10/05/2017 06:11 AM, Henrik Bengtsson wrote:
> I'd like to follow up/bump the attention to this bug causing the
> timeout to fail for socketSelect() on Unix. It is still there in R
> 3.4.2 and R-devel. I've identified the bug in the R source code - the
> bug is due to floating-point precisions and comparison using >=. See
> PR17203