search for: nething

I'm not an LDAP expert and I need an help to understand the following situation. I'm configuring a web LDAP addressbook (roundcube) against a Samba 4.4 DC to use simple binds over ldaps://. My troubles with Samba 4 DC start when the server response contains a referral with ldap:// URI scheme.  The client fails without messages to error logs. This does not happen against a Windows Server

> From: Jens Kraemer <jk at jkraemer.net> > Subject: Re: [Ferret-talk] Performance before and after optimization > On Sat, Nov 03, 2007 at 08:49:17PM +0800, Alex Neth wrote: > [..] >> 2) Can I keep a second index so that it doesn''t get locked during >> optimization and then switch to the optimized index? Perhaps the >> index >> is not really

Thanks Stuart. I thought I had read somewhere that rebuild_index built the index in a different location and then swapped it, but after looking at the code (in local_index.rb) this doesn''t appear to be the case. That might explain why the ferret server crashes sometimes when a search takes place during a reindex. I wouldn''t be doing exactly the same thing as this but

I have an index with a few hundred thousand records. The index is generally very fast, with sub 100ms responses. However if I start adding records, it gets extremely slow, up to over 2 seconds per query. This is true even if I am not currently indexing until I optimize the index. In order to work around this, I index in bulk and immediately optimize. This is not ideal for the

Hi all I am working on a heavy engineering project. And the requirement is that I needto do a lot of process before I store the data to the db. Now the question is that I want to do the process that I am doing but I want to do it in the background. What I actually mean to say is that..I just want the user to get a msg that Records Saved. But in real I want the process to go on in background.

Hi all, there was a recent thread[1] on rails-deploy about Ferret in which a lot of people complained of problems using it in production. I''ve been using Ferret (with DRb) for many months now with no serious issues. I''m assuming the posters know what they''re doing so I''m guessing they''re just using Ferret in higher-scale environments than me. I

Hi folks, Firstly, the first: dovecot --version 2.2.10 dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.16.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_debug = yes auth_krb5_keytab = /var/lib/dovecot/krb5.keytab auth_master_user_separator = * auth_mechanisms = plain login gssapi auth_verbose = yes debug_log_path = /dev/null default_process_limit = 400

Thanks for the response Jens. Indeed I am sorting by something other than relevancy, so that would explain it. Optimized, it''s extremely fast and handles a good load, but new records kill it until I optimize. I haven''t tried :merge_factor as I wasn''t aware of it. I''m not sure it will help given the above. Regarding the re-index locking code,

I have had to fix a few issues with AAF in order to get it working well for myself in a production environment. I''m using the latest "release" version which is 0.4.1: 1) When there is no index in place, every request starts a new rebuild. While there is some code in place to allow this to happen during testing, personally I see no reason to even test for this,

Dear R-friends, the dataset I am using (data.it) is organized as follows partner stp btp reg hk 0.64 1 s ger 0.27 1 d tur 0.27 1 s rom 0.24 1 s-f por 0.24 1 s spa 0.23 1 s gre 0.22 1 d-f aus 0.17 1 d uk 0.16 1 s be 0.16 1 d arg 0.15 1 s usa 0.13 1 d-f fra 0.13 1 s neth

Hi, folks. I am planning on implementing Asterisk in 2006, and need to budget for it now, so I need to know what I'll need to get. My company has about 50 users, and is currently languishing on a very old Comdial PBX. All of our client computers are Macs; our servers are mostly OS X, with a couple Debians and a Red Hat. I am thoroughly experienced at systems administration, and can

I''ve been running some multithreaded tests on Ferret. Using a single Ferret::Index::Index inside a DRb server, it definitely behaves for me as if all readers are locked out of the index when writing is going on in that index, not just optimization -- at least when segment merging happens, which is when the writes take the longest and you can therefore least afford to lock out all reads.