From nobody@FreeBSD.org  Thu Jun 10 05:33:42 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 80E771065670
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 10 Jun 2010 05:33:42 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 659658FC14
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 10 Jun 2010 05:33:42 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o5A5XfHt006790
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 10 Jun 2010 05:33:41 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o5A5Xf3r006789;
	Thu, 10 Jun 2010 05:33:41 GMT
	(envelope-from nobody)
Message-Id: <201006100533.o5A5Xf3r006789@www.freebsd.org>
Date: Thu, 10 Jun 2010 05:33:41 GMT
From: Martin Minkus <martin.minkus@punz.co.nz>
To: freebsd-gnats-submit@FreeBSD.org
Subject: open_socket_in: Protocol not supported - after a few days?
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         147756
>Category:       kern
>Synopsis:       [libc] open_socket_in: Protocol not supported - after a few days?
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jun 10 05:40:01 UTC 2010
>Closed-Date:    
>Last-Modified:  Wed Aug 11 11:00:16 UTC 2010
>Originator:     Martin Minkus
>Release:        8-STABLE
>Organization:
>Environment:
FreeBSD kinetic.pulse.local 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #4: Wed May 26 18:09:14 NZST 2010     martinm@kinetic.pulse.local:/usr/obj/usr/src/sys/PULSE  amd64

>Description:
Samba 3.4 on FreeBSD 8-STABLE branch.

After a few days I start getting weird errors and windows PC's can't
access the samba share, have trouble accessing files, etc, and samba
becomes totally unusable.

Restarting samba doesn't fix it, only a reboot does.

log.smb:

[2010/06/10 17:22:39,  0] lib/util_sock.c:902(open_socket_in)
  open_socket_in(): socket() call failed: Protocol not supported
[2010/06/10 17:22:39,  0] smbd/server.c:457(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Protocol not supported
[2010/06/10 17:22:39,  2] smbd/server.c:676(smbd_parent_loop)
  waiting for connections

log.ANYPC:

[2010/06/08 19:55:55,  0] lib/util_sock.c:1491(get_peer_addr_internal)
  getpeername failed. Error was Socket is not connected
  read_fd_with_timeout: client 0.0.0.0 read error = Socket is not connected.


The code in lib/util_sock.c, around line 902:

/****************************************************************************
 Open a socket of the specified type, port, and address for incoming data.
****************************************************************************/

int open_socket_in(int type,
                uint16_t port,
                int dlevel,
                const struct sockaddr_storage *psock,
                bool rebind)
{
        struct sockaddr_storage sock;  
        int res;
        socklen_t slen = sizeof(struct sockaddr_in);
         
        sock = *psock;
        
#if defined(HAVE_IPV6)
        if (sock.ss_family == AF_INET6) {
                ((struct sockaddr_in6 *)&sock)->sin6_port = htons(port);
                slen = sizeof(struct sockaddr_in6);
        }
#endif
        if (sock.ss_family == AF_INET) {
                ((struct sockaddr_in *)&sock)->sin_port = htons(port);
        }
                
        res = socket(sock.ss_family, type, 0 );
        if( res == -1 ) {
                if( DEBUGLVL(0) ) {                            
                        dbgtext( "open_socket_in(): socket() call failed: " );
                        dbgtext( "%s\n", strerror( errno ) );
                }

In other words, something in the kernel is being exhausted in my case
and some tuning is required as its failing to create sockets?


/boot/loader.conf:

mvs_load="YES"
zfs_load="YES"
vm.kmem_size="20G"

#vfs.zfs.arc_min="512M"
#vfs.zfs.arc_max="1536M"

vfs.zfs.arc_min="512M"
vfs.zfs.arc_max="3072M"

/etc/sysctl.conf:

kern.ipc.maxsockbuf=2097152

net.inet.tcp.sendspace=262144
net.inet.tcp.recvspace=262144
net.inet.tcp.mssdflt=1452

net.inet.udp.recvspace=65535
net.inet.udp.maxdgram=65535

net.local.stream.recvspace=65535
net.local.stream.sendspace=65535

(those don't seem to fix anything, btw.)

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:

From: Kirill A Sarksyan <dot@kkursor.ru>
To: bug-followup@FreeBSD.org, martin.minkus@punz.co.nz
Cc:  
Subject: Re: kern/147756: [libc] open_socket_in: Protocol not supported -
 after a few days?
Date: Mon, 09 Aug 2010 16:34:46 +0400

 --=-6p5pAF8Sjv1gnTThEges
 Content-Type: text/plain; charset="UTF-8"
 Content-Transfer-Encoding: 7bit
 
 I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul  1 01:27:47 MSD 2010.
 On start Samba log contains:
 [2010/08/09 16:19:04,  1] smbd/files.c:177(file_init)
   file_init: Information only: requested 16384 open files, 7014 are
 available.
 [2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
   open_socket_in(): socket() call failed: Protocol not supported
 [2010/08/09 16:19:04,  0] smbd/server.c:457(smbd_open_one_socket)
   smbd_open_once_socket: open_socket_in: Protocol not supported
 [2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
   open_socket_in(): socket() call failed: Protocol not supported
 [2010/08/09 16:19:04,  0] smbd/server.c:457(smbd_open_one_socket)
   smbd_open_once_socket: open_socket_in: Protocol not supported
 
 %pkg_info | grep samba
 samba34-3.4.8       A free SMB and CIFS client and server for UNIX
 
 And Windows clients cannot use Samba shares at all.
 
 
 
 --=-6p5pAF8Sjv1gnTThEges
 Content-Type: text/html; charset="utf-8"
 Content-Transfer-Encoding: 7bit
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
 <HTML>
 <HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
   <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
 </HEAD>
 <BODY>
 I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul&nbsp; 1 01:27:47 MSD 2010.<BR>
 On start Samba log contains:<BR>
 [2010/08/09 16:19:04,&nbsp; 1] smbd/files.c:177(file_init)<BR>
 &nbsp; file_init: Information only: requested 16384 open files, 7014 are available.<BR>
 [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<BR>
 &nbsp; open_socket_in(): socket() call failed: Protocol not supported<BR>
 [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<BR>
 &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
 [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<BR>
 &nbsp; open_socket_in(): socket() call failed: Protocol not supported<BR>
 [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<BR>
 &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
 <BR>
 %pkg_info | grep samba<BR>
 samba34-3.4.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A free SMB and CIFS client and server for UNIX<BR>
 <BR>
 And Windows clients cannot use Samba shares at all.<BR>
 <BR>
 <BR>
 </BODY>
 </HTML>
 
 --=-6p5pAF8Sjv1gnTThEges--
 

From: Kirill A Sarksyan <dot@kkursor.ru>
To: Martin Minkus <martin.minkus@pulseutilities.co.nz>
Cc: bug-followup <bug-followup@FreeBSD.org>
Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported -
 after a few days?
Date: Tue, 10 Aug 2010 01:31:56 +0400

 --=-Gm/lsWSUG+RZpBXZBoJ4
 Content-Type: text/plain; charset="UTF-8"
 Content-Transfer-Encoding: 8bit
 
 Strange. The computer I speak about works as my home server (including
 WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4.
 I found a strange thing - Samba correctly works from inside of home
 network, but fails to work from the Internet. I will re-read
 configuration how-to, maybe there is some differencies between old Samba
 and the new one, because of which new Samba does not listen globally
 available network interfaces.
 
 В Втр, 10/08/2010 в 09:23 +1200, Martin Minkus пишет:
 > In my case it was bad hardware. Seemed to be the PCI bus, so probably
 > the southbridge.
 > 
 >  
 > 
 > Anything using PCIe was completely unaffected, and mem tests running
 > for days passed fine.
 > 
 >  
 > 
 > Traffic going over the pci bus, even the onboard nic would silently
 > get corrupted.
 > 
 >  
 > 
 > Moved the hardware onto a new motherboard and all the issues magically
 > disappeared.....
 > 
 >  
 > 
 > 
 > From: Kirill A Sarksyan [mailto:dot@kkursor.ru] 
 > Sent: Tuesday, 10 August 2010 00:35
 > To: bug-followup@FreeBSD.org; Martin Minkus
 > Subject: Re: kern/147756: [libc] open_socket_in: Protocol not
 > supported - after a few days?
 > 
 > 
 > 
 >  
 > 
 > I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul  1 01:27:47 MSD
 > 2010.
 > On start Samba log contains:
 > [2010/08/09 16:19:04,  1] smbd/files.c:177(file_init)
 >   file_init: Information only: requested 16384 open files, 7014 are
 > available.
 > [2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
 >   open_socket_in(): socket() call failed: Protocol not supported
 > [2010/08/09 16:19:04,  0] smbd/server.c:457(smbd_open_one_socket)
 >   smbd_open_once_socket: open_socket_in: Protocol not supported
 > [2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
 >   open_socket_in(): socket() call failed: Protocol not supported
 > [2010/08/09 16:19:04,  0] smbd/server.c:457(smbd_open_one_socket)
 >   smbd_open_once_socket: open_socket_in: Protocol not supported
 > 
 > %pkg_info | grep samba
 > samba34-3.4.8       A free SMB and CIFS client and server for UNIX
 > 
 > And Windows clients cannot use Samba shares at all.
 > 
 > 
 > 
 > 
 
 
 --=-Gm/lsWSUG+RZpBXZBoJ4
 Content-Type: text/html; charset="utf-8"
 Content-Transfer-Encoding: 7bit
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
 <HTML>
 <HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
   <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
 </HEAD>
 <BODY LINK="#0000ff">
 Strange. The computer I speak about works as my home server (including WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4.<BR>
 I found a strange thing - Samba correctly works from inside of home network, but fails to work from the Internet. I will re-read configuration how-to, maybe there is some differencies between old Samba and the new one, because of which new Samba does not listen globally available network interfaces.<BR>
 <BR>
 &#1042; &#1042;&#1090;&#1088;, 10/08/2010 &#1074; 09:23 +1200, Martin Minkus &#1087;&#1080;&#1096;&#1077;&#1090;:
 <BLOCKQUOTE TYPE=CITE>
     In my case it was bad hardware. Seemed to be the PCI bus, so probably the southbridge.<BR>
     <BR>
     &nbsp;<BR>
     <BR>
     Anything using PCIe was completely unaffected, and mem tests running for days passed fine.<BR>
     <BR>
     &nbsp;<BR>
     <BR>
     Traffic going over the pci bus, even the onboard nic would silently get corrupted.<BR>
     <BR>
     &nbsp;<BR>
     <BR>
     Moved the hardware onto a new motherboard and all the issues magically disappeared.....<BR>
     <BR>
     &nbsp;<BR>
     <BR>
 </BLOCKQUOTE>
 <BLOCKQUOTE TYPE=CITE>
     <B>From:</B> Kirill A Sarksyan [mailto:dot@kkursor.ru] <BR>
     <B>Sent:</B> Tuesday, 10 August 2010 00:35<BR>
     <B>To:</B> bug-followup@FreeBSD.org; Martin Minkus<BR>
     <B>Subject:</B> Re: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days?<BR>
     <BR>
     <BR>
 </BLOCKQUOTE>
 <BLOCKQUOTE TYPE=CITE>
     &nbsp;<BR>
     <BR>
     I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul&nbsp; 1 01:27:47 MSD 2010.<BR>
     On start Samba log contains:<BR>
     [2010/08/09 16:19:04,&nbsp; 1] smbd/files.c:177(file_init)<BR>
     &nbsp; file_init: Information only: requested 16384 open files, 7014 are available.<BR>
     [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<BR>
     &nbsp; open_socket_in(): socket() call failed: Protocol not supported<BR>
     [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<BR>
     &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
     [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<BR>
     &nbsp; open_socket_in(): socket() call failed: Protocol not supported<BR>
     [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<BR>
     &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
     <BR>
     %pkg_info | grep samba<BR>
     samba34-3.4.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A free SMB and CIFS client and server for UNIX<BR>
     <BR>
     And Windows clients cannot use Samba shares at all.<BR>
     <BR>
     <BR>
     <BR>
     <BR>
 </BLOCKQUOTE>
 <BR>
 </BODY>
 </HTML>
 
 --=-Gm/lsWSUG+RZpBXZBoJ4--
 

From: Martin Minkus <martin.minkus@pulseutilities.co.nz>
To: bug-followup <bug-followup@FreeBSD.org>, dot <dot@kkursor.ru>
Cc:  
Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported - after
 a few days?
Date: Tue, 10 Aug 2010 09:23:21 +1200

 --2_0_c2_b54b62MHTML_=_01
 Content-Type: text/plain; charset=US-ASCII
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: inline
 
 In my case it was bad hardware. Seemed to be the PCI bus, so probably
 the southbridge.
 
 =20
 
 Anything using PCIe was completely unaffected, and mem tests running for
 days passed fine.
 
 =20
 
 Traffic going over the pci bus, even the onboard nic would silently get
 corrupted.
 
 =20
 
 Moved the hardware onto a new motherboard and all the issues magically
 disappeared.....
 
 =20
 
 From: Kirill A Sarksyan [mailto:dot@kkursor.ru]=20
 Sent: Tuesday, 10 August 2010 00:35
 To: bug-followup@FreeBSD.org; Martin Minkus
 Subject: Re: kern/147756: [libc] open_socket_in: Protocol not supported
 - after a few days?
 
 =20
 
 I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul  1 01:27:47 MSD 2010.
 On start Samba log contains:
 [2010/08/09 16:19:04,  1] smbd/files.c:177(file_init)
   file_init: Information only: requested 16384 open files, 7014 are
 available.
 [2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
   open_socket_in(): socket() call failed: Protocol not supported
 [2010/08/09 16:19:04,  0] smbd/server.c:457(smbd_open_one_socket)
   smbd_open_once_socket: open_socket_in: Protocol not supported
 [2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
   open_socket_in(): socket() call failed: Protocol not supported
 [2010/08/09 16:19:04,  0] smbd/server.c:457(smbd_open_one_socket)
   smbd_open_once_socket: open_socket_in: Protocol not supported
 
 %pkg_info | grep samba
 samba34-3.4.8       A free SMB and CIFS client and server for UNIX
 
 And Windows clients cannot use Samba shares at all.
 
 
 
 
 
 --2_0_c2_b54b62MHTML_=_01
 Content-Type: text/html
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: inline
 
 <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mi=
 crosoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:wo=
 rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D=
 "http://www.w3.org/TR/REC-html40">
 
 <head>
 
 <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
 <style>
 <!--
  /* Font Definitions */
  @font-face
 	{font-family:"Cambria Math";
 	panose-1:2 4 5 3 5 4 6 3 2 4;}
 @font-face
 	{font-family:Calibri;
 	panose-1:2 15 5 2 2 2 4 3 2 4;}
 @font-face
 	{font-family:Tahoma;
 	panose-1:2 11 6 4 3 5 4 4 2 4;}
  /* Style Definitions */
  p.MsoNormal, li.MsoNormal, div.MsoNormal
 	{margin:0cm;
 	margin-bottom:.0001pt;
 	font-size:12.0pt;
 	font-family:"Times New Roman","serif";}
 a:link, span.MsoHyperlink
 	{mso-style-priority:99;
 	color:blue;
 	text-decoration:underline;}
 a:visited, span.MsoHyperlinkFollowed
 	{mso-style-priority:99;
 	color:purple;
 	text-decoration:underline;}
 p
 	{mso-style-priority:99;
 	mso-margin-top-alt:auto;
 	margin-right:0cm;
 	mso-margin-bottom-alt:auto;
 	margin-left:0cm;
 	font-size:12.0pt;
 	font-family:"Times New Roman","serif";}
 span.EmailStyle18
 	{mso-style-type:personal-reply;
 	font-family:"Calibri","sans-serif";
 	color:#1F497D;}
 =2EMsoChpDefault
 	{mso-style-type:export-only;
 	font-size:10.0pt;}
 @page WordSection1
 	{size:612.0pt 792.0pt;
 	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
 div.WordSection1
 	{page:WordSection1;}
 -->
 </style>
 <!--[if gte mso 9]><xml>
  <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
 </xml><![endif]--><!--[if gte mso 9]><xml>
  <o:shapelayout v:ext=3D"edit">
   <o:idmap v:ext=3D"edit" data=3D"1" />
  </o:shapelayout></xml><![endif]-->
 </head>
 
 <body lang=3DEN-NZ link=3Dblue vlink=3Dpurple>
 
 <div class=3DWordSection1>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'>In my case it was bad hardware. Seemed to be the PCI bus, s=
 o
 probably the southbridge.<o:p></o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'><o:p>&nbsp;</o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'>Anything using PCIe was completely unaffected, and mem tes=
 ts
 running for days passed fine.<o:p></o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'><o:p>&nbsp;</o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'>Traffic going over the pci bus, even the onboard nic would=
 
 silently get corrupted.<o:p></o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'><o:p>&nbsp;</o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'>Moved the hardware onto a new motherboard and all the issu=
 es magically
 disappeared.....<o:p></o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'><o:p>&nbsp;</o:p></span>
 
 </p>
 
 <div>
 
 <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0c=
 m 0cm 0cm'>
 
 <p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font=
 -family:
 "Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-s=
 ize:10.0pt;
 font-family:"Tahoma","sans-serif"'> Kirill A Sarksyan [mailto:dot@kkursor=
 =2Eru] <br>
 
 <b>Sent:</b> Tuesday, 10 August 2010 00:35<br>
 
 <b>To:</b> bug-followup@FreeBSD.org; Martin Minkus<br>
 
 <b>Subject:</b> Re: kern/147756: [libc] open_socket_in: Protocol not supp=
 orted
 - after a few days?<o:p></o:p></span>
 
 </p>
 
 </div>
 
 </div>
 
 <p class=3DMsoNormal><o:p>&nbsp;</o:p>
 
 </p>
 
 <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>I confirm this on Fre=
 eBSD
 7.3-RELEASE #12: Thu Jul&nbsp; 1 01:27:47 MSD 2010.<br>
 
 On start Samba log contains:<br>
 
 [2010/08/09 16:19:04,&nbsp; 1] smbd/files.c:177(file_init)<br>
 
 &nbsp; file_init: Information only: requested 16384 open files, 7014 are
 available.<br>
 
 [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<br>
 
 &nbsp; open_socket_in(): socket() call failed: Protocol not supported<br>=
 
 
 [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<br=
 >
 
 &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<br>
 
 [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<br>
 
 &nbsp; open_socket_in(): socket() call failed: Protocol not supported<br>=
 
 
 [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<br=
 >
 
 &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<br>
 
 <br>
 
 %pkg_info | grep samba<br>
 
 samba34-3.4.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A free SMB and CIFS cli=
 ent
 and server for UNIX<br>
 
 <br>
 
 And Windows clients cannot use Samba shares at all.<br>
 
 <br>
 
 <o:p></o:p>
 
 </p>
 
 </div>
 
 </body>
 
 </html>
 --2_0_c2_b54b62MHTML_=_01--

From: Martin Minkus <martin.minkus@pulseutilities.co.nz>
To: dot <dot@kkursor.ru>
Cc: bug-followup <bug-followup@FreeBSD.org>
Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported - after
 a few days?
Date: Tue, 10 Aug 2010 09:41:38 +1200

 --2_0_2fd_b54f96MHTML_=_01
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: inline
 
 1) yes, you can specify what interfaces and what subnets it will allow
 connections from in smb.conf. Checking those settings will allow you to
 do what you want.
 
 2) However, you do not want samba open and accepting connections from
 the entire internet....... that=E2=80=99s bad. Set up a VPN using openvpn=
  or
 whatever to allow outside samba access to just those persons or sites
 that need it.
 
 =C2=A0
 
 Martin.
 
 =C2=A0
 
 From: Kirill A Sarksyan [mailto:dot@kkursor.ru]=20
 Sent: Tuesday, 10 August 2010 09:32
 To: Martin Minkus
 Cc: bug-followup
 Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported
 - after a few days?
 
 =C2=A0
 
 Strange. The computer I speak about works as my home server (including
 WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4.
 I found a strange thing - Samba correctly works from inside of home
 network, but fails to work from the Internet. I will re-read
 configuration how-to, maybe there is some differencies between old Samba
 and the new one, because of which new Samba does not listen globally
 available network interfaces.
 
 =D0=92 =D0=92=D1=82=D1=80, 10/08/2010 =D0=B2 09:23 +1200, Martin Minkus =D0=
 =BF=D0=B8=D1=88=D0=B5=D1=82:=20
 
 In my case it was bad hardware. Seemed to be the PCI bus, so probably
 the southbridge.
 
 =C2=A0
 
 Anything using PCIe was completely unaffected, and mem tests running for
 days passed fine.
 
 =C2=A0
 
 Traffic going over the pci bus, even the onboard nic would silently get
 corrupted.
 
 =C2=A0
 
 Moved the hardware onto a new motherboard and all the issues magically
 disappeared.....
 
 =C2=A0
 
    From: Kirill A Sarksyan [mailto:dot@kkursor.ru]=20
    Sent: Tuesday, 10 August 2010 00:35
    To: bug-followup@FreeBSD.org; Martin Minkus
    Subject: Re: kern/147756: [libc] open_socket_in: Protocol not
    supported - after a few days?
   =20
   =20
 
    =C2=A0
   =20
    I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul=C2=A0 1 01:27:47 MS=
 D
    2010.
    On start Samba log contains:
    [2010/08/09 16:19:04,=C2=A0 1] smbd/files.c:177(file_init)
    =C2=A0 file_init: Information only: requested 16384 open files, 7014 a=
 re
    available.
    [2010/08/09 16:19:04,=C2=A0 0] lib/util_sock.c:902(open_socket_in)
    =C2=A0 open_socket_in(): socket() call failed: Protocol not supported
    [2010/08/09 16:19:04,=C2=A0 0] smbd/server.c:457(smbd_open_one_socket)=
 
    =C2=A0 smbd_open_once_socket: open_socket_in: Protocol not supported
    [2010/08/09 16:19:04,=C2=A0 0] lib/util_sock.c:902(open_socket_in)
    =C2=A0 open_socket_in(): socket() call failed: Protocol not supported
    [2010/08/09 16:19:04,=C2=A0 0] smbd/server.c:457(smbd_open_one_socket)=
 
    =C2=A0 smbd_open_once_socket: open_socket_in: Protocol not supported
   =20
    %pkg_info | grep samba
    samba34-3.4.8=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 A free SMB and CIFS c=
 lient and server for UNIX
   =20
    And Windows clients cannot use Samba shares at all.
   =20
   =20
   =20
   =20
 
 =C2=A0
 
 
 
 --2_0_2fd_b54f96MHTML_=_01
 Content-Type: text/html
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: inline
 
 
 <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-mi=
 crosoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:wo=
 rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D=
 "http://www.w3.org/TR/REC-html40">
 
 <head>
 
 <meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
 <style>
 <!--
  /* Font Definitions */
  @font-face
 	{font-family:"Cambria Math";
 	panose-1:2 4 5 3 5 4 6 3 2 4;}
 @font-face
 	{font-family:Calibri;
 	panose-1:2 15 5 2 2 2 4 3 2 4;}
 @font-face
 	{font-family:Tahoma;
 	panose-1:2 11 6 4 3 5 4 4 2 4;}
  /* Style Definitions */
  p.MsoNormal, li.MsoNormal, div.MsoNormal
 	{margin:0cm;
 	margin-bottom:.0001pt;
 	font-size:12.0pt;
 	font-family:"Times New Roman","serif";}
 a:link, span.MsoHyperlink
 	{mso-style-priority:99;
 	color:blue;
 	text-decoration:underline;}
 a:visited, span.MsoHyperlinkFollowed
 	{mso-style-priority:99;
 	color:purple;
 	text-decoration:underline;}
 p
 	{mso-style-priority:99;
 	mso-margin-top-alt:auto;
 	margin-right:0cm;
 	mso-margin-bottom-alt:auto;
 	margin-left:0cm;
 	font-size:12.0pt;
 	font-family:"Times New Roman","serif";}
 p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
 	{mso-style-priority:34;
 	margin-top:0cm;
 	margin-right:0cm;
 	margin-bottom:0cm;
 	margin-left:36.0pt;
 	margin-bottom:.0001pt;
 	font-size:12.0pt;
 	font-family:"Times New Roman","serif";}
 span.EmailStyle18
 	{mso-style-type:personal-reply;
 	font-family:"Calibri","sans-serif";
 	color:#1F497D;}
 =2EMsoChpDefault
 	{mso-style-type:export-only;
 	font-size:10.0pt;}
 @page WordSection1
 	{size:612.0pt 792.0pt;
 	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
 div.WordSection1
 	{page:WordSection1;}
 -->
 </style>
 <!--[if gte mso 9]><xml>
  <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
 </xml><![endif]--><!--[if gte mso 9]><xml>
  <o:shapelayout v:ext=3D"edit">
   <o:idmap v:ext=3D"edit" data=3D"1" />
  </o:shapelayout></xml><![endif]-->
 </head>
 
 <body lang=3DEN-NZ link=3Dblue vlink=3Dpurple>
 
 <div class=3DWordSection1>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'>1) yes, you can specify what interfaces and what subnets i=
 t will
 allow connections from in smb.conf. Checking those settings will allow yo=
 u to
 do what you want.<o:p></o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'>2) However, you do not want samba open and accepting conne=
 ctions
 from the entire internet....... that&#8217;s bad. Set up a VPN using open=
 vpn or
 whatever to allow outside samba access to just those persons or sites tha=
 t need
 it.<o:p></o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'><o:p>&nbsp;</o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'>Martin.<o:p></o:p></span>
 
 </p>
 
 <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri=
 ","sans-serif";
 color:#1F497D'><o:p>&nbsp;</o:p></span>
 
 </p>
 
 <div>
 
 <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0c=
 m 0cm 0cm'>
 
 <p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font=
 -family:
 "Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-s=
 ize:10.0pt;
 font-family:"Tahoma","sans-serif"'> Kirill A Sarksyan [mailto:dot@kkursor=
 =2Eru] <br>
 
 <b>Sent:</b> Tuesday, 10 August 2010 09:32<br>
 
 <b>To:</b> Martin Minkus<br>
 
 <b>Cc:</b> bug-followup<br>
 
 <b>Subject:</b> RE: kern/147756: [libc] open_socket_in: Protocol not supp=
 orted
 - after a few days?<o:p></o:p></span>
 
 </p>
 
 </div>
 
 </div>
 
 <p class=3DMsoNormal><o:p>&nbsp;</o:p>
 
 </p>
 
 <p class=3DMsoNormal>Strange. The computer I speak about works as my home=
  server
 (including WWW- and Mail) for 2 years, I never had any issues, except Sam=
 ba
 3.4.<br>
 
 I found a strange thing - Samba correctly works from inside of home netwo=
 rk,
 but fails to work from the Internet. I will re-read configuration how-to,=
  maybe
 there is some differencies between old Samba and the new one, because of w=
 hich
 new Samba does not listen globally available network interfaces.<br>
 
 <br>
 
 &#1042; &#1042;&#1090;&#1088;, 10/08/2010 &#1074; 09:23 +1200, Martin Min=
 kus
 &#1087;&#1080;&#1096;&#1077;&#1090;: <o:p></o:p>
 
 </p>
 
 <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>In my case it was bad=
  hardware.
 Seemed to be the PCI bus, so probably the southbridge.<br>
 
 <br>
 
 &nbsp;<br>
 
 <br>
 
 Anything using PCIe was completely unaffected, and mem tests running for d=
 ays
 passed fine.<br>
 
 <br>
 
 &nbsp;<br>
 
 <br>
 
 Traffic going over the pci bus, even the onboard nic would silently get
 corrupted.<br>
 
 <br>
 
 &nbsp;<br>
 
 <br>
 
 Moved the hardware onto a new motherboard and all the issues magically
 disappeared.....<br>
 
 <br>
 
 &nbsp;<o:p></o:p>
 
 </p>
 
 <blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>
 
 <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b>From:</b> Kirill A=
  Sarksyan
 [mailto:dot@kkursor.ru] <br>
 
 <b>Sent:</b> Tuesday, 10 August 2010 00:35<br>
 
 <b>To:</b> bug-followup@FreeBSD.org; Martin Minkus<br>
 
 <b>Subject:</b> Re: kern/147756: [libc] open_socket_in: Protocol not supp=
 orted
 - after a few days?<br>
 
 <br>
 
 <o:p></o:p>
 
 </p>
 
 </blockquote>
 
 <blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>
 
 <p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>&nbsp;<br>
 
 <br>
 
 I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul&nbsp; 1 01:27:47 MSD 2=
 010.<br>
 
 On start Samba log contains:<br>
 
 [2010/08/09 16:19:04,&nbsp; 1] smbd/files.c:177(file_init)<br>
 
 &nbsp; file_init: Information only: requested 16384 open files, 7014 are
 available.<br>
 
 [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<br>
 
 &nbsp; open_socket_in(): socket() call failed: Protocol not supported<br>=
 
 
 [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<br=
 >
 
 &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<br>
 
 [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<br>
 
 &nbsp; open_socket_in(): socket() call failed: Protocol not supported<br>=
 
 
 [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<br=
 >
 
 &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<br>
 
 <br>
 
 %pkg_info | grep samba<br>
 
 samba34-3.4.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A free SMB and CIFS cli=
 ent
 and server for UNIX<br>
 
 <br>
 
 And Windows clients cannot use Samba shares at all.<br>
 
 <br>
 
 <br>
 
 <br>
 
 <o:p></o:p>
 
 </p>
 
 </blockquote>
 
 <p class=3DMsoNormal><o:p>&nbsp;</o:p>
 
 </p>
 
 </div>
 
 </body>
 
 </html>
 --2_0_2fd_b54f96MHTML_=_01--

From: Kirill A Sarksyan <dot@kkursor.ru>
To: Martin Minkus <martin.minkus@pulseutilities.co.nz>
Cc: bug-followup <bug-followup@FreeBSD.org>
Subject: RE: kern/147756: [libc] open_socket_in: Protocol not supported -
 after a few days?
Date: Wed, 11 Aug 2010 14:51:18 +0400

 --=-80mZ6+GDI4EpBIO08kxX
 Content-Type: multipart/alternative; boundary="=-Cd5wzKAum3n+wEjSPCOI"
 
 
 --=-Cd5wzKAum3n+wEjSPCOI
 Content-Type: text/plain; charset="UTF-8"
 Content-Transfer-Encoding: 8bit
 
 I know that it's not a good idea, though I want samba open over the
 entire Internets. Anonymous default user from teh Internets can do
 nothing, folders become available for authenticated users. I know about
 vulnerabilities, etc. :)
 In previous versions of Samba no interfaces directive was required and
 Samba listened all interfaces by default. Maybe this behaviour has
 changed in 3.4.
 I discovered a work-around. I will probably use FTP for storing backups
 from two office sites to my home server instead of SMB. Though Windoze
 likes SMB more than FTP. 
 Thank you. :)
 
 
 В Втр, 10/08/2010 в 09:41 +1200, Martin Minkus пишет:
 > 1) yes, you can specify what interfaces and what subnets it will allow
 > connections from in smb.conf. Checking those settings will allow you
 > to do what you want.
 > 
 > 2) However, you do not want samba open and accepting connections from
 > the entire internet....... that’s bad. Set up a VPN using openvpn or
 > whatever to allow outside samba access to just those persons or sites
 > that need it.
 > 
 >  
 > 
 > Martin.
 > 
 >  
 > 
 > 
 > From: Kirill A Sarksyan [mailto:dot@kkursor.ru] 
 > Sent: Tuesday, 10 August 2010 09:32
 > To: Martin Minkus
 > Cc: bug-followup
 > Subject: RE: kern/147756: [libc] open_socket_in: Protocol not
 > supported - after a few days?
 > 
 > 
 > 
 >  
 > 
 > Strange. The computer I speak about works as my home server (including
 > WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4.
 > I found a strange thing - Samba correctly works from inside of home
 > network, but fails to work from the Internet. I will re-read
 > configuration how-to, maybe there is some differencies between old
 > Samba and the new one, because of which new Samba does not listen
 > globally available network interfaces.
 > 
 > В Втр, 10/08/2010 в 09:23 +1200, Martin Minkus пишет: 
 > 
 > In my case it was bad hardware. Seemed to be the PCI bus, so probably
 > the southbridge.
 > 
 >  
 > 
 > Anything using PCIe was completely unaffected, and mem tests running
 > for days passed fine.
 > 
 >  
 > 
 > Traffic going over the pci bus, even the onboard nic would silently
 > get corrupted.
 > 
 >  
 > 
 > Moved the hardware onto a new motherboard and all the issues magically
 > disappeared.....
 > 
 >  
 > 
 > 
 >         From: Kirill A Sarksyan [mailto:dot@kkursor.ru] 
 >         Sent: Tuesday, 10 August 2010 00:35
 >         To: bug-followup@FreeBSD.org; Martin Minkus
 >         Subject: Re: kern/147756: [libc] open_socket_in: Protocol not
 >         supported - after a few days?
 >         
 >         
 >         
 >          
 >         
 >         I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul  1 01:27:47
 >         MSD 2010.
 >         On start Samba log contains:
 >         [2010/08/09 16:19:04,  1] smbd/files.c:177(file_init)
 >           file_init: Information only: requested 16384 open files,
 >         7014 are available.
 >         [2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
 >           open_socket_in(): socket() call failed: Protocol not
 >         supported
 >         [2010/08/09 16:19:04,  0]
 >         smbd/server.c:457(smbd_open_one_socket)
 >           smbd_open_once_socket: open_socket_in: Protocol not
 >         supported
 >         [2010/08/09 16:19:04,  0] lib/util_sock.c:902(open_socket_in)
 >           open_socket_in(): socket() call failed: Protocol not
 >         supported
 >         [2010/08/09 16:19:04,  0]
 >         smbd/server.c:457(smbd_open_one_socket)
 >           smbd_open_once_socket: open_socket_in: Protocol not
 >         supported
 >         
 >         %pkg_info | grep samba
 >         samba34-3.4.8       A free SMB and CIFS client and server for
 >         UNIX
 >         
 >         And Windows clients cannot use Samba shares at all.
 >         
 >         
 >         
 >         
 >         
 > 
 > 
 >  
 > 
 > 
 
 
 --=-Cd5wzKAum3n+wEjSPCOI
 Content-Type: text/html; charset="utf-8"
 Content-Transfer-Encoding: 7bit
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
 <HTML>
 <HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
   <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
 </HEAD>
 <BODY LINK="#0000ff">
 I know that it's not a good idea, though I want samba open over the entire Internets. Anonymous default user from teh Internets can do nothing, folders become available for authenticated users. I know about vulnerabilities, etc. <IMG SRC="cid:1281523741.2195.14.camel@notebook" ALIGN="middle" ALT=":)" BORDER="0"><BR>
 In previous versions of Samba no interfaces directive was required and Samba listened all interfaces by default. Maybe this behaviour has changed in 3.4.<BR>
 I discovered a work-around. I will probably use FTP for storing backups from two office sites to my home server instead of SMB. Though Windoze likes SMB more than FTP. <BR>
 Thank you. <IMG SRC="cid:1281523741.2195.14.camel@notebook" ALIGN="middle" ALT=":)" BORDER="0"><BR>
 <BR>
 <BR>
 &#1042; &#1042;&#1090;&#1088;, 10/08/2010 &#1074; 09:41 +1200, Martin Minkus &#1087;&#1080;&#1096;&#1077;&#1090;:
 <BLOCKQUOTE TYPE=CITE>
     1) yes, you can specify what interfaces and what subnets it will allow connections from in smb.conf. Checking those settings will allow you to do what you want.<BR>
     <BR>
     2) However, you do not want samba open and accepting connections from the entire internet....... that&#8217;s bad. Set up a VPN using openvpn or whatever to allow outside samba access to just those persons or sites that need it.<BR>
     <BR>
     &nbsp;<BR>
     <BR>
     Martin.<BR>
     <BR>
     &nbsp;<BR>
     <BR>
 </BLOCKQUOTE>
 <BLOCKQUOTE TYPE=CITE>
     <B>From:</B> Kirill A Sarksyan [mailto:dot@kkursor.ru] <BR>
     <B>Sent:</B> Tuesday, 10 August 2010 09:32<BR>
     <B>To:</B> Martin Minkus<BR>
     <B>Cc:</B> bug-followup<BR>
     <B>Subject:</B> RE: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days?<BR>
     <BR>
     <BR>
 </BLOCKQUOTE>
 <BLOCKQUOTE TYPE=CITE>
     &nbsp;<BR>
     <BR>
     Strange. The computer I speak about works as my home server (including WWW- and Mail) for 2 years, I never had any issues, except Samba 3.4.<BR>
     I found a strange thing - Samba correctly works from inside of home network, but fails to work from the Internet. I will re-read configuration how-to, maybe there is some differencies between old Samba and the new one, because of which new Samba does not listen globally available network interfaces.<BR>
     <BR>
     &#1042; &#1042;&#1090;&#1088;, 10/08/2010 &#1074; 09:23 +1200, Martin Minkus &#1087;&#1080;&#1096;&#1077;&#1090;: <BR>
     <BR>
     In my case it was bad hardware. Seemed to be the PCI bus, so probably the southbridge.<BR>
     <BR>
     &nbsp;<BR>
     <BR>
     Anything using PCIe was completely unaffected, and mem tests running for days passed fine.<BR>
     <BR>
     &nbsp;<BR>
     <BR>
     Traffic going over the pci bus, even the onboard nic would silently get corrupted.<BR>
     <BR>
     &nbsp;<BR>
     <BR>
     Moved the hardware onto a new motherboard and all the issues magically disappeared.....<BR>
     <BR>
     &nbsp;<BR>
     <BR>
     <BLOCKQUOTE>
         <B>From:</B> Kirill A Sarksyan [mailto:dot@kkursor.ru] <BR>
         <B>Sent:</B> Tuesday, 10 August 2010 00:35<BR>
         <B>To:</B> bug-followup@FreeBSD.org; Martin Minkus<BR>
         <B>Subject:</B> Re: kern/147756: [libc] open_socket_in: Protocol not supported - after a few days?<BR>
         <BR>
         <BR>
         <BR>
         &nbsp;<BR>
         <BR>
         I confirm this on FreeBSD 7.3-RELEASE #12: Thu Jul&nbsp; 1 01:27:47 MSD 2010.<BR>
         On start Samba log contains:<BR>
         [2010/08/09 16:19:04,&nbsp; 1] smbd/files.c:177(file_init)<BR>
         &nbsp; file_init: Information only: requested 16384 open files, 7014 are available.<BR>
         [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<BR>
         &nbsp; open_socket_in(): socket() call failed: Protocol not supported<BR>
         [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<BR>
         &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
         [2010/08/09 16:19:04,&nbsp; 0] lib/util_sock.c:902(open_socket_in)<BR>
         &nbsp; open_socket_in(): socket() call failed: Protocol not supported<BR>
         [2010/08/09 16:19:04,&nbsp; 0] smbd/server.c:457(smbd_open_one_socket)<BR>
         &nbsp; smbd_open_once_socket: open_socket_in: Protocol not supported<BR>
         <BR>
         %pkg_info | grep samba<BR>
         samba34-3.4.8&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A free SMB and CIFS client and server for UNIX<BR>
         <BR>
         And Windows clients cannot use Samba shares at all.<BR>
         <BR>
         <BR>
         <BR>
         <BR>
         <BR>
     </BLOCKQUOTE>
     <BR>
     &nbsp;<BR>
     <BR>
     <BR>
 </BLOCKQUOTE>
 <BR>
 </BODY>
 </HTML>
 
 --=-Cd5wzKAum3n+wEjSPCOI--
 
 --=-80mZ6+GDI4EpBIO08kxX
 Content-ID: <1281523741.2195.14.camel@notebook>
 Content-Disposition: attachment; filename="face-smile.png"
 Content-Type: image/png; name="face-smile.png"
 Content-Transfer-Encoding: base64
 
 iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABmJLR0QA/wD/AP+gvaeTAAAAB3RJ
 TUUH1wgOER8RqU5d7gAAAwtJREFUOI1lk01oXGUYhZ/73Ts/sWPiT8YE2ti6SF00jDWBaBWLuhFB
 QgUNQsFdCair2pVSBV3YGkNWDVjcqKlIaG2sLf5EUBqTBkqjTFMi2Px2ojOTpJnMZHLnfvd+3+si
 VKR5V2dxOBx4z+Nw1419QZty3R5EdYmJmgEcpfIgF6zYT59+nan/+5074sYQ8XIQG/ASjYdbDxyP
 px58Rql4M0hIFMxQKf5sb149pY1eOdOQ4I193ej/AoaGcFt07PKufUc6dmY+ShBOI+FfQAB4ID5C
 CieeYWHy3SA/c/FaLsHB7m4MABNfxfpvTfb4YkpiNi+K1X+K2EDEhiKmIhIVxNauil55R6LNUZkZ
 e96fGKQfwBn7jN3xhqZsx8tT9aInUYlOTvSeYrlYoK/3fcRWOdk7wHJxiY8/eBZdPo/X8BZ/XHql
 HG5UM0olvaOtT7yXIprF8fYALmfPfcPwt5dANNgyZ8+PMPzdOJh/wOQx/ii7M6+mSHJU4ahDqfRz
 SqJ5cGIgNR5t3Uv7/gxifbDr7H0kxeNtOxB9A3Aw/jip9EHlCIc8G0VNKpZGdBGiHOI+xODnJ0FC
 xK6AKfDl6ZcgmkOiRcBg9QLJB1qwliYPAIkQKUM4DbYETt1WfSmDWQa7BraKNTXEBohoQADwHNct
 mGD+YSUKMXkc8cFJbhlsFbFrYFYRW8KaDazxQaUJ/XmUoqAEM1wufG/xdkK0xOTICW4v/YKuTmP0
 AjbMEdYWWc3Pcv1KFmMquHWdVJYvW3EY3nrjvfdl27t+qpfKaW5X2slN9VEtLWEiDYDredxT38iu
 treJywB16Q/J/nikHG5UM1tDGlT9c1de9CN/XMK1T8TUrok1ayJWi9hAbLQqYXVUqn+/KUHpa5n5
 7anNO0PyABbj9pi9+UOniNPR8tjxRLgxgvF/xeg5xAY4bhq37gDejhe4db2vVpwb/z2X4Ng2mNZr
 DLjx+w/v2f9aPNX4pIolW0AsoT9LZWXCLmTPaaPXzzQk74JpG84OPQJdWJoBUOQduGCFbTj/C8H3
 uN+XWOgHAAAAAElFTkSuQmCC
 
 
 --=-80mZ6+GDI4EpBIO08kxX--
 
>Unformatted:
