Displaying 20 results from an estimated 2379 matches for "recving".
Did you mean:
receving
2002 May 04
2
Failure to update differing file
I have two large files (2+MB), one of which is a corrupted version of
the other. I tried to rsync the good file to the corrupted one,
hoping it would repair the few bad bytes, but it did nothing. (I
tried to be careful not to specify the --archive or --update flags,
either explicitly or implicitly.)
The original problem occurrend on a transfer from one computer to
another. I then did a number
2005 Jul 20
0
rsync breaks suddenly
Hi,
I am trying to mirror a suse part with rsync -tvvvvvvrl
--delete-excluded --stats --progress --exclude i386/9.1-personal-iso/
--exclude i386/live*/
ftp.gwdg.de::pub/linux/suse/ftp.suse.com/suse/i386/
/var/ftp/pub/suse/i386 2&> rsync.log
Randomly it hangs and after about 15 minutes I am getting an error. I've
copied the last lines of my log:
set modtime of
2018 Mar 01
29
[Bug 13317] New: rsync returns success when target filesystem is full
https://bugzilla.samba.org/show_bug.cgi?id=13317
Bug ID: 13317
Summary: rsync returns success when target filesystem is full
Product: rsync
Version: 3.1.2
Hardware: x64
OS: FreeBSD
Status: NEW
Severity: major
Priority: P5
Component: core
Assignee: wayned at samba.org
2008 Jul 29
3
ipfw "bug" - recv any = not recv any
I hesitate to call this a "bug" as I don't know all the history behind
the ipfw2 decisions, so let me toss this out there and see I'm just
missing something.
Overview
========
The negated operator, "not recv any" was taken to mean "any packet never
received by an interface" believed to be equivalent to "any packet that
originated on the current
2006 Nov 12
0
[ wxruby-Bugs-6632 ] Linux crash on NoteBook in bigdemo.rb
Bugs item #6632, was opened at 2006-11-12 16:45
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=218&aid=6632&group_id=35
Category: Incorrect behavior
Group: None
Status: Open
Resolution: None
Priority: 4
Submitted By: Alex Fenton (brokentoy)
Assigned to: Kevin Smith (qualitycode)
Summary: Linux crash on NoteBook in bigdemo.rb
Initial Comment:
Linux
2015 Nov 14
1
[PATCH v2] pmu: fix queued messages while getting no IRQ
I encountered while stresstesting the reclocking code, that rarely (1 out of
20.000+ requests) we don't get any IRQ in nvkm_pmu_intr.
This means we have a queued message on the pmu, but nouveau doesn't read it and
waits infinitely in nvkm_pmu_send:
if (reply) {
wait_event(pmu->recv.wait, (pmu->recv.process == 0));
therefore let us use wait_event_timeout with a 1s timeout frame
2007 Feb 05
2
recv vs. read in HTTPRequest#read_socket
Hello all,
The following change to Mongrel::HttpRequest:
def read_socket(len)
if !@socket.closed?
data = @socket.recv(len) # <--- formerly @socket.read(len)
if !data
raise "Socket read return nil"
elsif data.length != len
raise "Socket read returned insufficient data: #{data.length}"
else
data
end
else
raise "Socket
2001 Dec 20
0
Annoying error (read_socket_data: recv failure for 4)
Hello all,
I'm having troubles with a samba 2.2.2 server (on debian). Some clients are
having problems connecting, and are filling the logs with messages like
those below. This isn't the first time I've had this problem, nor is it the
first site. This is a win98 box I'm having troubles with now - it fails
trying to log onto the domain... although I'm fairly sure it affects
2015 Nov 14
0
[PATCH] pmu: fix queued messages while getting no IRQ
I encountered while stresstesting the reclocking code, that rarely (1 out of
20.000+ requests) we don't get any IRQ in nvkm_pmu_intr.
This means we have a queued message on the pmu, but nouveau doesn't read it and
waits infinitely in nvkm_pmu_send:
if (reply) {
wait_event(pmu->recv.wait, (pmu->recv.process == 0));
therefore let us use wait_event_timeout with a 1s timeout frame
2015 Nov 14
0
[PATCH v3] pmu: fix queued messages while getting no IRQ
I encountered while stresstesting the reclocking code, that rarely (1 out of
20.000+ requests) we don't get any IRQ in nvkm_pmu_intr.
This means we have a queued message on the pmu, but nouveau doesn't read it and
waits infinitely in nvkm_pmu_send:
if (reply) {
wait_event(pmu->recv.wait, (pmu->recv.process == 0));
therefore let us use wait_event_timeout with a 1s timeout frame
2004 Jan 21
0
Samba ver 2.2.2 - socket read - WinXP
Jan. 21, 2004
Dear All,
I have enjoyed some success with Samba version 2.2.2. I am using
it to serve Micro$ Access to end users. It works very well on a prior
version of Unix, with older Win2k clients. Now, with my current version,
and Win XP Pro, I have problems. Periodically, they get abruptly kicked out.
I get syslog errors which look like:
kforce-adm-# tail syslog
Jan 7 16:29:09
2016 Mar 01
2
[PATCH 0/2] PMU communications improvements
Both patches should make the communicating with the PMU more stable.
Karol Herbst (2):
pmu: fix queued messages while getting no IRQ
pmu: be more strict about locking
drm/nouveau/nvkm/subdev/pmu/base.c | 49 ++++++++++++++++++++++++++++++++------
1 file changed, 42 insertions(+), 7 deletions(-)
--
2.7.2
2009 Apr 01
0
[ANNOUNCE] conntrack-tools 0.9.12 released
Hi!
The netfilter project presents another development release of the
conntrack-tools that includes a new `-S' option for the command line
tool, and a generic infrastructure to allow using different protocols to
replicate state-changes, currently unicast UDP and multicast are supported.
= command line interface: conntrack =
* Add `-S' option to display in-kernel connection tracking
2011 Oct 04
1
libvir: Remote error : cannot recv data: : Connection reset by peer
I'm using Libvirt's Java API and connecting to the hypervisor using the
same. My program is such that periodic discovery of active VMs is done using
Libvirt's functions.
However, when I try to perform any VM related operations while the Java code
connecting to Qemu is running such as shutdown, start VM using virsh, I end
up with :
'libvir: Remote error : cannot recv data: :
2018 Dec 21
1
[nbdkit PATCH] connections: Don't use uninit memory on early client EOF
Fuzzing with afl found a bug where a 27 byte client sequence
can cause nbdkit to report a strange error message:
$ printf %s $'000\1IHAVEOPT000\6'$'000\7'$'000\1x00' | tr 0 '\0' |
./nbdkit -s memory size=1m >/dev/null
nbdkit: memory: error: client exceeded maximum number of options (32)
The culprit? The client is hanging up on a message boundary,
so
2019 Jun 03
0
[PATCH libnbd discussion only 3/5] lib: Pass handle to socket recv and send calls.
Just a simple refactoring in preparation for forthcoming work.
---
generator/states-reply.c | 2 +-
generator/states.c | 4 ++--
lib/crypto.c | 5 +++--
lib/internal.h | 6 ++++--
lib/socket.c | 5 +++--
5 files changed, 13 insertions(+), 9 deletions(-)
diff --git a/generator/states-reply.c b/generator/states-reply.c
index 5be3431..f0ef47c 100644
---
2009 Sep 04
2
Xen & netperf
First, I apologize if this message has been received multiple times.
I''m having problems subscribing to this mailing list:
Hi xen-users,
I am trying to decide whether I should run a game server inside a Xen
domain. My primary reason for wanting to virtualize is because I want
to isolate this environment from the rest of my server. I really like
the idea of isolating the game server
2003 May 02
1
WARNING (Sipsock_read) Recv error: Resource temporaily unavailable
Greetings
I am receiving following error message. Any idea as to why?
WARNING[147466]: File chan_sip.c, Line 4530 (sipsock_read): Recv error:
Resource temporarily unavailable
WARNING[147466]: File chan_sip.c, Line 4530 (sipsock_read): Recv error:
Resource temporarily unavailable
Frank...
2013 Oct 20
1
backup maildir mailbox bugs
Hi,
Using dovecot v2.2.5.5, I get the following:
$ doveadm -v backup -R -u user at example.com maildir:/home/rsync/
example.com/user/Maildir/
[...]
dsync(user at example.com): Panic: file dsync-mailbox-export.c: line 228
(export_save_change_get): assertion failed: (change->type ==
DSYNC_MAIL_CHANGE_TYPE_FLAG_CHANGE)
dsync(user at example.com): Error: Raw backtrace:
2009 Nov 19
3
ZFS send / recv to a lower ZFS version
Hi,
We are using multiple opensolaris 06/09 and solaris 10 servers.
Currently we are ''dumping'' (incremental)backups to a backup server. I
wonder if anybody knows what happens when I send/recv a zfs volume from
version 15 to a (backup) system with version 14. I''ve the feeling it''s
not very wise to do, but is it doable and what kind of caveats can be