Date: Tue, 2 Apr 2002 11:43:25 -0600 From: "David W. Chapman Jr." <dwcjr@inethouston.net> To: Jens Rehsack <rehsack@liwing.de> Cc: "David W. Chapman Jr." <dwcjr@inethouston.net>, Scott Reese <sreese@codysbooks.com>, dwcjr@FreeBSD.org, ports@FreeBSD.org Subject: Re: FreeBSD Port: samba-2.2.3a Message-ID: <20020402174325.GE96062@leviathan.inethouston.net> In-Reply-To: <3CA9EC90.E23CAEF8@liwing.de> References: <1017690918.281.36.camel@borges.codysbooks.com> <20020401211916.GB42309@leviathan.inethouston.net> <3CA9DEBA.3155BC05@liwing.de> <20020402170206.GA96062@leviathan.inethouston.net> <3CA9EC90.E23CAEF8@liwing.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 02, 2002 at 07:38:24PM +0200, Jens Rehsack wrote: > > I'm not sure I'm understanding the timing, is that the time samba was > > upgraded to 2.2.3a or freebsd changes were made. Also are you > > building with any special options? > > No, I didn't build with any special options at this time. > But I got the same behaviour of nmbd, and I thought expirience this could > be interesting. > Sorry wasting your time. > Its not a waste of my time, I'm just trying to figure out exactly what's going on. Whether you think its FreeBSD that changed or samba that changed when it started to break. It may not be a ports problem but a problem the samba team has to fix or that there is a bug in FreeBSD. So I ask again, do you think FreeBSD changed or did samba change when this started to happen? -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. <www.inethouston.net> dwcjr@freebsd.org FreeBSD Committer <www.FreeBSD.org> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020402174325.GE96062>