From owner-freebsd-net@FreeBSD.ORG Fri Apr 7 19:39:47 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92EDC16A41A for ; Fri, 7 Apr 2006 19:39:47 +0000 (UTC) (envelope-from qgyang@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23F7443D5D for ; Fri, 7 Apr 2006 19:39:47 +0000 (GMT) (envelope-from qgyang@gmail.com) Received: by wproxy.gmail.com with SMTP id i34so434549wra for ; Fri, 07 Apr 2006 12:39:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:user-agent:date:subject:from:to:message-id:thread-topic:thread-index:mime-version:content-type:content-transfer-encoding; b=BnxO7LTDZuEQ+4oHVuQ4lQScqyuVunp1UNOJIVSz2gVJQD1FFS/CpJTPGQuRwY0osANXwnnVHPoRqmaPYbTigrLeRfAlTpypfw89LmBf8ktpRGopxtL0X4wQC1Hrx4uzusIV4GOKfpskZYLttI6NHNCAP+uzENE5nnlFRNc2baE= Received: by 10.65.219.6 with SMTP id w6mr911838qbq; Fri, 07 Apr 2006 12:39:46 -0700 (PDT) Received: from ?192.168.5.93? ( [64.154.93.163]) by mx.gmail.com with ESMTP id e10sm375825qbe.2006.04.07.12.39.45; Fri, 07 Apr 2006 12:39:46 -0700 (PDT) User-Agent: Microsoft-Entourage/11.2.3.060209 Date: Fri, 07 Apr 2006 12:39:41 -0700 From: Qiao Yang To: Message-ID: Thread-Topic: Unreliable Unix Domain DGRAM socket? Thread-Index: AcZaewNUQfZFHcZuEdqE4gANkytcAg== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Unreliable Unix Domain DGRAM socket? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2006 19:39:47 -0000 Hi all, Does anyone know what possible scenarios may cause the Unix Domain DGRAM socket to lose packet? We know, in theory, it is unreliable, but in reality, I rarely see packet loss happens to this type of socket. Unfortunately, I believe it happened a few times in the last couple of months in a FreeBSD 5.3 box and I wasn't able to track down what the cause was. One related question. Considering the following setup, client (socket_A) send a packet to server (socket_B). If the sending buffer of socket_A is ok but the receiving buffer of socket_B is full, will sendto() return error? Thanks for your insights. --Qiao