On Fri, 2003-03-28 at 17:17, Tim Potter wrote:
> On Thu, Mar 27, 2003 at 09:41:55PM -0800, Richard Sharpe wrote:
>
> > On Fri, 28 Mar 2003, Tim Potter wrote:
> >
> > > I was poking around in the segv signal handling code today as I'm in a
> > > situation where an actual core dump would be handy t
On Thu, Mar 27, 2003 at 09:41:55PM -0800, Richard Sharpe wrote:
> On Fri, 28 Mar 2003, Tim Potter wrote:
>
> > I was poking around in the segv signal handling code today as I'm in a
> > situation where an actual core dump would be handy to have.
> >
> > The intent of the current code looks like
On Fri, 28 Mar 2003, Tim Potter wrote:
> I was poking around in the segv signal handling code today as I'm in a
> situation where an actual core dump would be handy to have.
>
> The intent of the current code looks like core dumps are to be made in
> $LOGDIR/corefiles but the dump_core() function
I was poking around in the segv signal handling code today as I'm in a
situation where an actual core dump would be handy to have.
The intent of the current code looks like core dumps are to be made in
$LOGDIR/corefiles but the dump_core() function is never executed as the
argument to fault_setup(
am in an ADS domain. From a Windows client, create a file, add a group
> to the file using ACLs (new means the group is not in winbindd database
> yet), the group is mapped as a user in the winbindd_idmap.tdb. The group
> is not any special type, just a normal group (not local, not universal).
>
> Anyone knows about this problem?
>
> Thanks,
> Chere
Fresh compile, Redhat Linux 7.3, rather standard installations on it.
This is what I get with log level 10 on winbindd when trying to list users.
The "need 0 more for a full request" part of the entry seems, well, interesting. Any
ideas?
Thanks,
Nir.
[2003/03/10 22:10:17, 10
On 8 Mar 2003, Andrew Bartlett <[EMAIL PROTECTED]> wrote:
> On Sat, 2003-03-08 at 21:20, Tim Potter wrote:
> > On Sat, Mar 08, 2003 at 09:10:23PM +1100, Andrew Bartlett wrote:
> >
> > > Is there any reason I should not apply this patch to Samba HEAD?
> >
> > I think the patch was eaten by Mailma
On Sat, 2003-03-08 at 21:20, Tim Potter wrote:
> On Sat, Mar 08, 2003 at 09:10:23PM +1100, Andrew Bartlett wrote:
>
> > Is there any reason I should not apply this patch to Samba HEAD?
>
> I think the patch was eaten by Mailman. Please re-send as text/plain.
>
> Without even seeing the patch (-
On Sat, Mar 08, 2003 at 09:10:23PM +1100, Andrew Bartlett wrote:
> Is there any reason I should not apply this patch to Samba HEAD?
I think the patch was eaten by Mailman. Please re-send as text/plain.
Without even seeing the patch (-: it's definitely a good idea.
Tim.
Is there any reason I should not apply this patch to Samba HEAD?
The current locking scheme in winbind is a complete mess - indeed, the
next step should be to push the locking into cli_full_connection(), but
I'll leave it for now.
This patch works on the noted behaviour that 2 parts of the connec
I'm using winbindd to dump NT users and groups out to Unix, and I think I've
found a rather major bug.
We have a mixture of Active Directory and WinNT Domains spread world-wide
over low to high (1-2Mbs) speed WAN links.
If I dump a remote domains groups, the accounts within show u
On Tue, 18 Feb 2003, Guenther Deschner wrote:
> hi,
>
> On Tue, Feb 18, 2003 at 05:57:55PM +0200, Nir Soffer wrote:
> > Our product uses Samba as a component. In our product we were forced to
> > modify certain parts of Samba, namely:
> >
> > Winbindd running
Very well then - but this might seriously screw up wrapping:
Our product uses Samba as a component. In our product we were forced to modify certain
parts of Samba, namely:
Winbindd running over TCP (to a remote host)
Smbd listening to an additional "failover" port.
Allow listen
On Tue, 18 Feb 2003, Guenther Deschner wrote:
> you have forgotten to add that patchfile :)
Note that since last month the Samba listserver has started filtering
message attachments:
http://lists.samba.org/pipermail/samba-technical/2003-January/041954.html
Inline your patches in the message bod
hi,
On Tue, Feb 18, 2003 at 05:57:55PM +0200, Nir Soffer wrote:
> Our product uses Samba as a component. In our product we were forced to
> modify certain parts of Samba, namely:
>
> Winbindd running over TCP (to a remote host)
this sounds very interesting.
> Smbd listening t
Our product uses Samba as a component. In our product we were forced to modify certain
parts of Samba, namely:
Winbindd running over TCP (to a remote host)
Smbd listening to an additional "failover" port.
Allow listening on non-broadcast interfaces.
All these changes are very minimal
Good point about non-smbd processes being winbindd clients. I've got
some myself :-)
Also agreed about benefits of shutting down idle connections -- just not
done yet.
Ken
Ken Cross
Network Storage Solutions
Phone 865.675.4070 ext 31
[EMAIL PROT
Ken Cross wrote:
I was suggesting the other way around -- the number of winbindd fd's
shouldn't be more than the max # of smbd's (well, maybe a *few* more).
But if you are having a system hard limit of 1024 FDs per process,
for example, which you can't raise via setrl
descriptors.
There's currently a "max smbd processes" in 3.0. Would that suffice for
max number of fd's for winbindd?
It might; I'm not sure how winbindd and smbd are tied together
(I don't use it myself...)
3. Provide a definition on Solaris for FD_SETSIZE befor
I was suggesting the other way around -- the number of winbindd fd's
shouldn't be more than the max # of smbd's (well, maybe a *few* more).
Ken
-Original Message-
From: Michael Steffens [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 15, 2003 11:18 AM
To: Ken Cross
r
(more accurate) ways of tracking this, and for winbindd you'll likely
have different requirements...
--
__
Michael Sweet, Easy Software Products [EMAIL PROTECTED]
Printing Software for UNIX http://www.easysw.com
descriptors.
There's currently a "max smbd processes" in 3.0. Would that suffice for
max number of fd's for winbindd?
I don't think so. It's not desireable to restrict the number
of smbds to the number of FDs that winbindd can have
simultanously, IMHO.
Michael
f
>file descriptors.
There's currently a "max smbd processes" in 3.0. Would that suffice for
max number of fd's for winbindd?
> 3. Provide a definition on Solaris for FD_SETSIZE before
>including so that the correct version of
>select() is use
Mike Sweet wrote:
Sooo, my recommendations are as follows:
1. Provide a configure option (--with-maxfiles or similar)
to configure the upper limit you want to support in SAMBA.
2. Provide a smb.conf option to control the max number of
file descriptors.
3. Provide a defin
Michael Steffens wrote:
...
I'm wondering, basically concerning all platforms, whether this
is about the size of fd_set, or about the number of FDs the
kernel will actually assign to a process.
If the latter one is not limited, wouldn't a single excessive FD
consumer impact other processes?
Som
Michael:
It's both. I hadn't mentioned it, but I also had to add this to
winbindd:
rlim.rlim_cur = 1500; // Files
rlim.rlim_max = rlim.rlim_cur;
stat = setrlimit( RLIMIT_NOFILE, &rlim );
if( stat != 0 ) DEBUG(0, ("Failed to set file limits: %s",
s
David Collier-Brown -- Customer Engineering wrote:
Ken Cross wrote:
#define FD_SETSIZE 2048 /* Max # of winbindd connections */
must occur before the first invocation of .
This could be a build option, but it might be much simpler to hard-code
it in local.h, which is what I did to fix it
Michael Steffens wrote:
Ken Cross wrote:
There is pretty much a one-to-one correspondence between the number of
smbd processes open (i.e. connected users) and winbindd file descriptors
(per fstat).
Hmm, it may be platform specific. smbd connects winbindd both directly
and via NSS. On HP-UX
Ken Cross wrote:
> > #define FD_SETSIZE 2048 /* Max # of winbindd connections */
> >
> > must occur before the first invocation of .
> >
> > This could be a build option, but it might be much simpler to hard-code
> > it in local.h, which is what I did to fi
Ken Cross wrote:
There is pretty much a one-to-one correspondence between the number of
smbd processes open (i.e. connected users) and winbindd file descriptors
(per fstat).
Hmm, it may be platform specific. smbd connects winbindd both directly
and via NSS. On HP-UX it consumes two client pipes
There is pretty much a one-to-one correspondence between the number of
smbd processes open (i.e. connected users) and winbindd file descriptors
(per fstat).
I think forking would be counter-productive since winbindd caches so
much stuff. A lot of it's in tdb files, though, so...
Frankly
Better yet: Have winbindd fork the same way smbd does, on a per-client
basis.
Someone should probably figure out what quality of the example network
caused winbindd to consume so many sockets. Are there really that many
requests being queued up at once? Shifting to a forking model would simply
On 12 Feb 2003, Michael Steffens <[EMAIL PROTECTED]> wrote:
> It's 60 by default after installation, but is tunable (with reboot).
Maybe hp should sell per-fd licences :-/
> The solution (and this should also work on other platforms) was to
> have winbindd housekeep its c
On Wed, Feb 12, 2003 at 10:23:14PM +, [EMAIL PROTECTED] wrote:
> > Better still why not use poll() instead of select() in the winbindd
> > main loop?
>
> Because not everyone has poll() :-(. Some have poll build on select.
> Some people have poll() and it doesn't
On Thu, Feb 13, 2003 at 09:03:54AM +1100, Tim Potter wrote:
> On Wed, Feb 12, 2003 at 04:26:21PM -0500, Michael B. Allen wrote:
>
> > > This is set at compile-time, not run-time. This line:
> > >
> > > #define FD_SETSIZE 2048 /* Max # of winbindd connections
On Wed, Feb 12, 2003 at 04:26:21PM -0500, Michael B. Allen wrote:
> > This is set at compile-time, not run-time. This line:
> >
> > #define FD_SETSIZE 2048 /* Max # of winbindd connections */
> >
> > must occur before the first invocation of .
> >
>
Storage Solutions
Phone 865.675.4070 ext 31
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Michael B. Allen
Sent: Wednesday, February 12, 2003 4:26 PM
To: Ken Cross
Cc: [EMAIL PROTECTED]
Subject: Re: Winbindd limited by select
On Wed
On Wed, 12 Feb 2003 07:36:19 -0500
"Ken Cross" <[EMAIL PROTECTED]> wrote:
> I've run into a problem with winbindd in both 2.2.x and 3.0 where it
> just locks up after a while on large, busy networks.
>
> We finally tracked down the problem to the fact that the
On Wed, Feb 12, 2003 at 07:36:19AM -0500, Ken Cross wrote:
> Samba-folk:
>
> I've run into a problem with winbindd in both 2.2.x and 3.0 where it
> just locks up after a while on large, busy networks.
>
> We finally tracked down the problem to the fact that the C library
> -Original Message-
> From: Ken Cross [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 12, 2003 3:41 PM
> To: Nir Soffer; 'Tim Potter'; [EMAIL PROTECTED]
> Subject: RE: winbindd losing trust relationship once in a
> while (Samba 3.0)
>
>
>
Hi Ken,
Ken Cross wrote:
I've run into a problem with winbindd in both 2.2.x and 3.0 where it
just locks up after a while on large, busy networks.
We finally tracked down the problem to the fact that the C library
"select" function is limited by default to 256 file descriptors
ry 12, 2003 8:15 AM
To: Tim Potter; [EMAIL PROTECTED]
Subject: RE: winbindd losing trust relationship once in a while (Samba
3.0)
[snip]
>
> I wonder whether the trusted domains patch that went by today
> fixes this
> as well? Would you mind trying it?
Since the patch doesn'
ED]]
> Sent: Wednesday, February 12, 2003 7:36
> To: 'Multiple recipients of list SAMBA-TECHNICAL'
> Subject: Winbindd limited by select
>
>
> Samba-folk:
>
> I've run into a problem with winbindd in both 2.2.x and 3.0 where it
> just locks up after a while
[snip]
>
> I wonder whether the trusted domains patch that went by today
> fixes this
> as well? Would you mind trying it?
Since the patch doesn't apply to a20, and I couldn't be bothered to check why properly
- I downloaded the CVS version, for the hell of it. The patch didn't apply to that
Samba-folk:
I've run into a problem with winbindd in both 2.2.x and 3.0 where it
just locks up after a while on large, busy networks.
We finally tracked down the problem to the fact that the C library
"select" function is limited by default to 256 file descriptors in
NetBSD (
PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Tim Potter
Sent: Wednesday, February 12, 2003 5:55 AM
To: Nir Soffer
Cc: [EMAIL PROTECTED]
Subject: Re: winbindd losing trust relationship once in a while (Samba
3.0)
On Wed, Feb 12, 2003 at 10:47:38AM +0200, Nir Soffer wrote:
> Scenario: Fr
patibility mode.
>
> Under certain combinations winbindd seems to be losing it's capability to contact
>the parent DC.
>
> Samba 3.0a20 works, spordically, unless you do some things (wbinfo -m, see below).
> Samba 3.0a21 doesn't work at all for me.
>
> Attached
Scenario: Fresh compile of Samba 3.0, both a20 and a21. Attempt to use attached
smb.conf.
EXANET-QA is a part of the EXANET-IL domain (e.g - EXANET-IL is the parent domain).
EXANET-QA is supposedly set in compatibility mode.
Under certain combinations winbindd seems to be losing it&#
hp CR1501 and friends
This patch tries to make winbindd cope with the security option
'restrict anonymous=1' on NT4 and W2kS. When this option is set, the
DC disallows SAMR calls on unauthenticated connections, but does allow
LSA translations between names and sids.
Obviously winb
On Sun, Jan 05, 2003 at 11:21:02PM -0500, Ken Cross wrote:
> Sure, it isn't obvious.
>
> "start" isn't where the list is in number of entries, it's an index into
> some data structure (coming from the DC, I think). The num_entries
> would increment by 513 (in my tests), but cli_samr_enum_dom_grou
o: Ken Cross
Cc: [EMAIL PROTECTED]
Subject: Re: Winbindd problem enumerating lots of groups
On Sun, Jan 05, 2003 at 07:22:33PM -0500, Ken Cross wrote:
> I found and fixed a problem where winbindd had trouble enumerating
> *lots* of groups (~2000 in my case). This is in SAMBA_3_0, but it's
On Sun, Jan 05, 2003 at 07:22:33PM -0500, Ken Cross wrote:
> I found and fixed a problem where winbindd had trouble enumerating
> *lots* of groups (~2000 in my case). This is in SAMBA_3_0, but it's in
> other versions, too.
>
> The problem was in the enum_dom_groups routi
I found and fixed a problem where winbindd had trouble enumerating
*lots* of groups (~2000 in my case). This is in SAMBA_3_0, but it's in
other versions, too.
The problem was in the enum_dom_groups routine in winbindd_rcp.c, line
153:
do {
struct acct_info *info2 = NULL;
uint32
hello everybody,
just a short question: is there any technical reason why domain local
groups are only implemented in winbind with native-mode win2k domains and
disabled in mixed-modes?
thanks a lot,
--
Guenther Deschner [EMAIL PROTECTED]
SuSE Linux AG
On Sun, 2002-12-01 at 01:46, [EMAIL PROTECTED] wrote:
> Good catch - thanks. I've fixed this in a differnt way,
> could you please look at the patch and confirm it's ok ?
Hi,
I just cvs-update'd and tried it out -- everything works fine for me :)
thanks,
domi.
--
Dominik 'Aeneas' Schnitzer <[E
On Sun, Dec 01, 2002 at 12:45:12AM +0100, Dominik 'Aeneas' Schnitzer wrote:
> Hi,
>
> Using CVS-HEAD I hit the following bug in winbind, in
>
> libsmb/namequery.c#get_dc_list():
> The code piece to remove duplicate entrys/zeroed IPs is buggy. basically
> it sets the number of DCs found to -1 if n
Hi,
Using CVS-HEAD I hit the following bug in winbind, in
libsmb/namequery.c#get_dc_list():
The code piece to remove duplicate entrys/zeroed IPs is buggy. basically
it sets the number of DCs found to -1 if no dupe/zeroed IP was detected.
It's fixed very easily :) I've attached a patch for libsmb
Andrew,
Killing nscd fixed the problem. thanks for the pointer
Matt McC
> Matthew McCowan wrote:
>>
>> running samba 2.2.5 on a solaris 2.7 with winbindd pointing to an NT4
>> PDC.
>>
>> Occasionally winbindd will hand out the wrong uid to a user trying to
>
> Matthew McCowan wrote:
>>
>> running samba 2.2.5 on a solaris 2.7 with winbindd pointing to an NT4
>> PDC.
>>
>> Occasionally winbindd will hand out the wrong uid to a user trying to
>> attach to the solaris box thru any PAM enabled service (telnet, smb
Matthew McCowan wrote:
>
> Howdy all,
>
> running samba 2.2.5 on a solaris 2.7 with winbindd pointing to an NT4 PDC.
>
> Occasionally winbindd will hand out the wrong uid to a user trying to attach
> to the solaris box thru any PAM enabled service (telnet, smbd, ssh, etc)
Howdy all,
running samba 2.2.5 on a solaris 2.7 with winbindd pointing to an NT4 PDC.
Occasionally winbindd will hand out the wrong uid to a user trying to attach
to the solaris box thru any PAM enabled service (telnet, smbd, ssh, etc).
For example Alice will login to a shell using her normal
> Please check this out - thanks !
>
> Jeremy.
>
> Index: nmbd/nmbd_logonnames.c
> ===
> RCS file: /data/cvs/samba/source/nmbd/nmbd_logonnames.c,v
> retrieving revision 1.11
> diff -u -r1.11 nmbd_logonnames.c
> --- nmbd/nmbd_logonname
D lookup before it
tries to dynamically allocate.
Basically, I was wondering what was meant by "hook for utilizing a
centralized winbindd id map database". Who's idea that was, and
perhaps get some ideas on what people want regarding this.
Also, I finally did do testing with t
On Tue, Oct 08, 2002 at 09:39:29AM +0200, Volker Lendecke wrote:
> On Mon, Oct 07, 2002 at 05:35:35PM -0400, Kevin Stefanik wrote:
> > from log.nmbd:
> > process_node_status_request: status request for name U_MTPPI<1c> from IP
> > 192.168.92.56 on subnet UNICAST_SUBNET.
>
> I had the same proble
On Tue, 8 Oct 2002, Kevin Stefanik wrote:
> Okay, then. I'm attaching what I'm using... I just moved your registration
> line into the _success function so it gets called for each subnet (basically
> subnet->ip) on which the server successfully registers 0x1c. I'll just hope
> that 2.2.6 wil
Okay, then. I'm attaching what I'm using... I just moved your registration
line into the _success function so it gets called for each subnet (basically
subnet->ip) on which the server successfully registers 0x1c. I'll just hope
that 2.2.6 will have this fixed one way or another and I can go b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I do have one question, though. If a samba PDC has multiple interfaces, would
> you want the PDC role registered with the PDC's ip on each interface? I
> think that would be accomplished if your insert_permanent_name_into_unicast
> were moved i
That's a much cleaner solution than what I was proposing. Thanks.
I do have one question, though. If a samba PDC has multiple interfaces, would
you want the PDC role registered with the PDC's ip on each interface? I
think that would be accomplished if your insert_permanent_name_into_unicast
On Mon, Oct 07, 2002 at 05:35:35PM -0400, Kevin Stefanik wrote:
> from log.nmbd:
> process_node_status_request: status request for name U_MTPPI<1c> from IP
> 192.168.92.56 on subnet UNICAST_SUBNET.
I had the same problem, and patched nmbd a bit. I'm not sure it's
the right fix, but here it is. W
I'm trying to get winbindd working (2.2.6pre2) but it won't start because it
claims to not find the domain controller (Samba as PDC) that the rest of the
network is happily using.
-d10 output from winbindd:
Could not open a connection to U_MTPPI for \P
ven't found the time to finish up yet. I had some other thoughts for
a slight rearrangement of the plug-in entry points.
Mike
On Fri, 2002-10-04 at 12:22, Gerald Carter wrote:
> On Thu, 3 Oct 2002, Josh Durham wrote:
>
> > I hacked winbindd to use 'flat files', s
On Thu, 3 Oct 2002, Josh Durham wrote:
> I hacked winbindd to use 'flat files', such as /etc/passwd and
> /etc/group. When winbindd gets a request to map a sid to an uid, it
> will now check to see if that account already exists in a flat file.
> If it
ed
on a 'first come, first serve' basis.
SOLUTION
I hacked winbindd to use 'flat files', such as /etc/passwd and
/etc/group. When winbindd gets a request to map a sid to an uid, it
will now check to see if that account already exists in a flat file.
If it does, it will
jerry,
Finally got a chance to try upgrade and 3.0alpha20 does resolve the
problemThanks,
chuck
Gerald Carter <[EMAIL PROTECTED]> on 09/30/2002 08:58:09 AM
To:[EMAIL PROTECTED]
cc:[EMAIL PROTECTED]
Subject:Re: Server name being truncated in Winbindd
On Thu,
At 11:42 01.10.2002 +0200, Stefan (metze) Metzmacher wrote:
>Hi all,
>
>here's a patch witch adds a -D option and -V option to winbindd.
>
>I think smbd, nmbd and wrepld have also this options and so it would be
>nice to keep them in sync.
>
>I also update the docu
Hi all,
here's a patch witch adds a -D option and -V option to winbindd.
I think smbd, nmbd and wrepld have also this options and so it would be
nice to keep them in sync.
I also update the docu for this change.
On Thu, 26 Sep 2002 [EMAIL PROTECTED] wrote:
> I am runing Samba-3.0-alpha18 winbindd and attempting to join a w2k
> domain that has a 15 character server name.. as you can see from the log
> below the name gets truncated to 14 characters which then resul
Well it is the W2k DC that has the 15 character name, not the client I
am attempting to join a Samba 3.0 client to a
w2k DC with a 15 character name... True it's not probably winbindd per se,
it just happens that I am using the "net rpc join" and winbindd to validate
users...
On Thu, 26 Sep 2002 [EMAIL PROTECTED] wrote:
> I am runing Samba-3.0-alpha18 winbindd and attempting to join a w2k domain
> that has a
> 15 character server name.. as you can see from the log below the name gets
> truncated to 14 characters which then re
I am runing Samba-3.0-alpha18 winbindd and attempting to join a w2k domain
that has a
15 character server name.. as you can see from the log below the name gets
truncated to 14 characters which then results in the NT_STATUS_INVALID_COMPUTER_NAME
when attempting authenticationI am not at work
On Mon, Sep 23, 2002 at 03:14:34PM +0200, Kim R. Pedersen wrote:
> Hello Winbindd-Fans,
>
> During my port of winbindd to my company's new platform, I have come across
> three memory leaks in winbindd.
>
> They are all related to misconfigured "password server"
I did not see any information on this, but it is in relation to build
failure (sigh, is it because gnu ld does not work on sco openserver?). Does
winbind not work on sco?
I used the following script to build after cvs head download:
#!/bin/ksh
cd /usr/local/samba/source
/usr/local/bin/make real
Hello Winbindd-Fans,
During my port of winbindd to my company's new platform, I have come across
three memory leaks in winbindd.
They are all related to misconfigured "password server" parameter, and
therefore not critical for "normal" environments.
As I'm wo
gt;
> I would prefer if there was a "direct" alternative, not requiring PAM.
> Mainly for simplicity of administration, but also because we have to
> support some systems not using PAM...
Yes, maintaining the squid stuff separate to the OS has it's advantages.
> Bt
tive, not requiring PAM.
Mainly for simplicity of administration, but also because we have to
support some systems not using PAM...
Btw, is it at all possible to build winbindd on systems not supporting PAM
and/or NSS?
> But if it just 'falls out' of the design (we will want one
On Fri, 2002-08-02 at 03:10, Ferguson, Ross wrote:
>
> rebuilding winbindd with the enclosed replacement function gets the UNIX
> uid/gid from the users home directory. If it fails in anyway, it returns
> (g/u)id of 'nobody' This obviously allows specifically ass
Title: winbindd: Here's a replacement get_id_from_sid() that gets UNIX uid/gid from /home/dir
rebuilding winbindd with the enclosed replacement function gets the UNIX uid/gid from the users home directory. If it fails in anyway, it returns (g/u)id of 'nobody' This o
ers, so it seemed the perfect beast for trialing the pam_winbind/winbindd
authentication mechanism.
The build went reasonably smoothly, and produced stuff that Solaris 7 was
happy with.
A configuration was arrived at that worked - the smb.conf from the 2.0.7
days was modified to include winbind, nss
I was wondering if anyone has done any scalability tests with
Samba+Winbindd to authenticate against AD Domains?
If we try to use Samba+Winbindd with say 50,000+ users what would the
response time be when authenticating 1,000's of users when they log into
their machines at 8:00AM?
As some user requested (sorry can't find the email to reply directly),
today I put options in swat to start stop restart also winbind (in HEAD)
Testing is welcome in testing it correctly detects if winbind is up or
not.
Simo.
--
Simo Sorce
--
Una scelta di liberta': Software Libero.
A
Mike Gerdts wrote:
> On Thu, 2002-07-18 at 02:03, Bogdan Iamandei wrote:
>
>
>>1). I don't seem to be able to specify multiple ranges of ID's for
>>winbindd. For example:
>>
>>winbind uid = 1000-2 25000-3
>>
>>Would this be
On Thu, 2002-07-18 at 02:03, Bogdan Iamandei wrote:
> 1). I don't seem to be able to specify multiple ranges of ID's for
> winbindd. For example:
>
> winbind uid = 1000-2 25000-3
>
> Would this be possible in the future? :) Please? :)
>
&g
Alexander Bokovoy wrote:
> On Wed, Jul 17, 2002 at 04:23:14PM +1000, Bogdan Iamandei wrote:
>
>> I am trying to make winbindd talk to the local AD swerver here
>>and it is not too clear to me whether there's a difference between
>>2.2.6-pre and 3.0-pre.
>>
On Wed, Jul 17, 2002 at 04:23:14PM +1000, Bogdan Iamandei wrote:
> I am trying to make winbindd talk to the local AD swerver here
> and it is not too clear to me whether there's a difference between
> 2.2.6-pre and 3.0-pre.
>
> It seems to me that 2.2.6-pre i
Hi everybody,
I am trying to make winbindd talk to the local AD swerver here
and it is not too clear to me whether there's a difference between
2.2.6-pre and 3.0-pre.
It seems to me that 2.2.6-pre is not really working (unless I
am doing somehthing wrong) and 3.0-p
On Sat, Jul 13, 2002 at 04:21:47AM +0930, Richard Sharpe wrote:
:
> > > We have to node status to get the *name* of the PDC, becouse the
> > > NETLOGON RPC requires that. Windows machines to a NETLOGON Mailslot
> > > message, but we don't do that at present.
> >
> > So you join the domain withou
On Thu, 11 Jul 2002, Christopher R. Hertel wrote:
> On Fri, Jul 12, 2002 at 10:44:54AM +1000, Andrew Bartlett wrote:
> > "Christopher R. Hertel" wrote:
> >
> > > Anyway, if the unexpected.tdb is the reason that winbindd needs nmbd, then
> > > I think
On Fri, Jul 12, 2002 at 10:44:54AM +1000, Andrew Bartlett wrote:
> "Christopher R. Hertel" wrote:
>
> > Anyway, if the unexpected.tdb is the reason that winbindd needs nmbd, then
> > I think it could be made optional. I imagine that winbindd would be
> > sendin
needs to be running on the local system as there are some lookup
> > > > requests send by winbindd that are sent by Windows NT domain controllers
> > > > to the incorrect port which is a bug in Windows. ?Nmbd receives these
> > > > packets and stores them in a
"Christopher R. Hertel" wrote:
> Anyway, if the unexpected.tdb is the reason that winbindd needs nmbd, then
> I think it could be made optional. I imagine that winbindd would be
> sending regular name queries in order to find the PDC, probably looking
> for #1B. The 1B a
1 - 100 of 147 matches
Mail list logo
