(4.2.0pre1-GIT-b505111; actually only
using client) behaviour #2 - accept: Software caused connection abort.
On Sun, 2013-08-25 at 18:50 +0100, Tris Mabbs wrote:
Probably should have posted this to samba-technical
in the first place, so re-posting in case anyone has any useful ideas
On Thu, Aug 29, 2013 at 10:10:38AM +0100, Tris Mabbs wrote:
Hiya Andrew,
Many thanks for the typically helpful and comprehensive reply :-)
I think that's probably the right track :-)
The code here is triggered when poll() indicates that the socket is
readable.
This socket should
.
-Original Message-
From: Jeremy Allison [mailto:j...@samba.org]
Sent: 29 August 2013 20:52
To: Tris Mabbs
Cc: 'Andrew Bartlett'; samba@lists.samba.org; samba-techni...@samba.org
Subject: Re: [Samba] Odd Samba 4 (4.2.0pre1-GIT-b505111; actually only
using client) behaviour #2 - accept: Software caused
On Sun, 2013-08-25 at 18:50 +0100, Tris Mabbs wrote:
Probably should have posted this to samba-technical in the
first place, so re-posting in case anyone has any useful ideas .
From: Tris Mabbs
Sent: 12 August 2013 23:08
To: 'samba@lists.samba.org'
Subject: Odd Samba
Probably should have posted this to samba-technical in the
first place, so re-posting in case anyone has any useful ideas .
From: Tris Mabbs
Sent: 12 August 2013 23:08
To: 'samba@lists.samba.org'
Subject: Odd Samba 4 (4.2.0pre1-GIT-b505111; actually only using client)
Caught it in the act! As predicted, almost immediately
after sending my original message (!) .
However unfortunately, it's not particularly useful .
...
16327: write(7, \0, 1)= 1
16327: setcontext(0xFEFFD690)
16327:
Good day oh technical ones .
I was running Samba 4 (client only, not using it as a DC so
effectively running Samba 3 code from the Samba 4 tree) and, other than a
little Gotcha! regarding decoding Kerberos PACs, it was all working
perfectly.
