search for: _assume_

Displaying 12 results from an estimated 12 matches for "_assume_".

2019 Feb 23
2
winbind causing huge timeouts/delays since 4.8
...> Unix, sssd, winbind and the ldap lines in smb.conf), they could all be > combined in AD. > > The main problem is that the OP wants Samba changing to cope with his > mess, it might be a valid change, but the reason for the change is > invalid. Well, I think the problem is you _assume_ users are in multiple databases and we just don't know that. I think there is a good change Alexander perfectly knows what he is doing and users are unique across databases. Nevertheless, at some point nss is clearly querying winbind, which means nss did not find the user in either /etc/passwd...
2004 Dec 05
1
Group sip definitions?
...e set of group sip.conf phone definitions that can be used by multiple internal sip phones (as in 50/group for example). Something like: [All-Sales] type=friend username=* secret=sales99 callgroup=9 pickupgroup=9 [All-CustServ] type=friend username=* secret=cs88 callgroup=8 pickupgroup=8 If we _assume_ all sip phones are of the same type (eg, C7940's), is there a way to provide a single definition (such as All-Sales in the above example) that can be used by multiple phones keying off the 'secret=' to establish business oriented groupings? (Sort of like approaching plug-n-play at the...
2019 Feb 23
2
winbind causing huge timeouts/delays since 4.8
...they could all >>> be combined in AD. >>> >>> The main problem is that the OP wants Samba changing to cope with >>> his mess, it might be a valid change, but the reason for the change >>> is invalid. >> >> Well, I think the problem is you _assume_ users are in multiple >> databases and we just don't know that. I think there is a good change >> Alexander perfectly knows what he is doing and users are unique >> across databases. >> >> Nevertheless, at some point nss is clearly querying winbind, which >>...
2006 Jul 12
3
Still trying to sort out an override problem
The program I am trying to run quits with the following error messages: fixme:richedit:RichEditANSIWndProc EM_EXLIMITTEXT: stub fixme:richedit:RichEditANSIWndProc EM_EXLIMITTEXT: stub fixme:richedit:RichEditANSIWndProc EM_EXLIMITTEXT: stub fixme:richedit:RichEditANSIWndProc EM_EXLIMITTEXT: stub fixme:richedit:RichEditANSIWndProc EM_EXLIMITTEXT: stub fixme:richedit:RichEditANSIWndProc
2019 Feb 23
0
winbind causing huge timeouts/delays since 4.8
...dap lines in smb.conf), they could all > > be combined in AD. > > > > The main problem is that the OP wants Samba changing to cope with > > his mess, it might be a valid change, but the reason for the change > > is invalid. > > Well, I think the problem is you _assume_ users are in multiple > databases and we just don't know that. I think there is a good change > Alexander perfectly knows what he is doing and users are unique > across databases. > > Nevertheless, at some point nss is clearly querying winbind, which > means nss did not find...
2019 Feb 23
0
winbind causing huge timeouts/delays since 4.8
...e combined in AD. > >>> > >>> The main problem is that the OP wants Samba changing to cope with > >>> his mess, it might be a valid change, but the reason for the > >>> change is invalid. > >> > >> Well, I think the problem is you _assume_ users are in multiple > >> databases and we just don't know that. I think there is a good > >> change Alexander perfectly knows what he is doing and users are > >> unique across databases. > >> > >> Nevertheless, at some point nss is clearly queryin...
2019 Feb 23
3
winbind causing huge timeouts/delays since 4.8
...more to glibc related. Removing winbind from nss fixed the freeze, but isn't an option. It leads to the point that asking winbind for an uknown user without domain took a long time before it returns WBC_ERR_DOMAIN_NOT_FOUND . >>>> >>>> Well, I think the problem is you _assume_ users are in multiple >>>> databases and we just don't know that. I think there is a good >>>> change Alexander perfectly knows what he is doing and users are >>>> unique across databases. >>>> >>>> Nevertheless, at some point nss is c...
2005 Jun 14
2
Questions about contexts
I'm trying to clarify contexts and their uses. I do have a good general understanding of them. My question is about "undeclared" and "non-existant" contexts. If I have a block somewhere (in sip.conf, for example), and it has no "context=thiscontext" field, does it just automatically use the "default" context? Or is this settable? (I see there is an
2019 Feb 23
2
winbind causing huge timeouts/delays since 4.8
> On 23 Feb 2019, at 09:33, Rowland Penny via samba <samba at lists.samba.org> wrote: > > If you have, as you have, 'files sss winbind' in the the passwd & group > line in nsswitch.conf, means this: > First /etc/passwd or /etc/group is searched and if the user or group is > found, this info is returned. > Next sssd will be asked, 'do you know this user
2019 Feb 23
0
winbind causing huge timeouts/delays since 4.8
...returns > WBC_ERR_DOMAIN_NOT_FOUND . You see, there you have 2 methods checking for the same thing, also the problem you are referring to has been fixed in the latest Samba (I think it has also been backported). > > >>>> > >>>> Well, I think the problem is you _assume_ users are in multiple > >>>> databases and we just don't know that. I think there is a good > >>>> change Alexander perfectly knows what he is doing and users are > >>>> unique across databases. > >>>> > >>>> Nevertheles...
2007 Nov 24
13
Bug#452721: xen-utils-common: "xendomains" does not restore domains in same order as it would start them
Package: xen-utils-common Version: 3.0.3-0-2 Severity: wishlist The "xendomains" init script will start domains according to the order of config files found in /etc/xen/auto/*. I use this so that, in the event of a hard reboot, the more important domains will start first. Some of these contain essential services like DNS resolvers, slapd and so on, and since starting xen domains
2019 Feb 26
3
winbind causing huge timeouts/delays since 4.8
...UND . > > You see, there you have 2 methods checking for the same thing, also the > problem you are referring to has been fixed in the latest Samba (I > think it has also been backported). > >> >>>>>> >>>>>> Well, I think the problem is you _assume_ users are in multiple >>>>>> databases and we just don't know that. I think there is a good >>>>>> change Alexander perfectly knows what he is doing and users are >>>>>> unique across databases. >>>>>> >>>>>&...