similar to: PDC (can't fetch domain SID)

Hi all, I have a RHEL5-update 3 x86_64 system, and I installed Samba 3.2.14-40 (from http://ftp.sernet.com/pub/samba/tested/rhel/5/x86_64/ ). I'm using OpenLDAP ( 2.3.43-3.el5 ,comes with RHEL5u3) as backend for winbind+samba in my PDC. With samba-3.0.33 that comes with RHEL5u3, i dont get that "eventlogadm" works how explain in http://wiki.samba.org/index.php/Event_Logging: For

Hello i use samba 3.025c testparm says that "passdb expand explicit" is deprecated but it seems to be working (i mean if i put %N in sambaProfilePath with passdb expand explicit set to yes, it is expanded) my question is : is this option deprecated? according to releases notes, only default value has changed to no....

So I went to the rails wiki to check some OSS projects in ruby and I get a bunch garbage for drug ads. WTF? http://wiki.rubyonrails.com/rails/pages/OpenSourceProjects -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060417/f234d115/attachment.html

Hi, I have had a problem report from a Recoll user about the amount of writes during index creation. https://opensourceprojects.eu/p/recoll1/tickets/67/ The issue is that the index is on SSD and that the amount of writes is significant compared to the SSD life expectancy (index size > 250 GB). >From the numbers he supplied, it seems to me that the total amount of block writes is roughly

I created a form with two collection_select, country and state and would like to bring up to date the state list when to select a new country. How I can make this in Rails? Thanks Eleudson Brazil <p><label for="person_country_id">Country</label><br/> <%= collection_select(:person, :country_id, @countries, :id, :name) %></p> <p><label

A Recoll user gets the following message while indexing: "Attempted to delete or modify an entry in a non-existent posting list for #bannerholder" The exception happens during a commit call. Xapian version 1.4.11, Debian Buster A little more detail here: https://opensourceprojects.eu/p/recoll1/tickets/108/ I asked if this was reproducible, and to run the indexing in single-thread

This is the latest development release and may be found at: http://shorewall.net/pub/shorewall/2.3/shorewall-2.3.1 ftp://shorewall.net/pub/shorewall/2.3/shorewall-2.3.1 This release changes the way that SAVE_IPSETS=Yes works to try to make it harder to shoot yourself in the foot. Read the release notes carefully. In addition, there are two problems corrected: 1) A typo in the

Is there any project which was recommende for reading it''s source for studing rails? such as typo ? -- Posted via http://www.ruby-forum.com/.

On Mon, Jan 21, 2019 at 03:25:01PM +0100, Jean-Francois Dockes wrote: > I have had a problem report from a Recoll user about the amount of writes > during index creation. > > https://opensourceprojects.eu/p/recoll1/tickets/67/ > > The issue is that the index is on SSD and that the amount of writes is > significant compared to the SSD life expectancy (index size > 250 GB).

On Mon, Aug 26, 2019 at 09:42:09AM +0200, Jean-Francois Dockes wrote: > A Recoll user gets the following message while indexing: > > "Attempted to delete or modify an entry in a non-existent posting list for #bannerholder" > > The exception happens during a commit call. Xapian version 1.4.11, Debian Buster > > A little more detail here:

On 14/09/2018 at 09:30, Jean-Francois Dockes wrote: > Hi, > > You may be interested by how Recoll does it: > > https://www.lesbonscomptes.com/recoll/idxthreads/threadingRecoll.html > > A few things in the document are slightly obsolete (esp. the last > paragraph: recollindex now does use vfork()), but it's overall quite close > to how the current indexer works.

This is quite possibly part of the underlying write explosion that we ran into when we wrote: https://fastmail.blog/2014/12/01/email-search-system/ Which now almost 5 years on, has been running like a champion! We're really pleased with how well it works. Xapian reads from multiple databases are really easy, and the immediate writes onto tmpfs and daily compacts work really well. We also

Olly Betts writes: > On Mon, Jan 21, 2019 at 03:25:01PM +0100, Jean-Francois Dockes wrote: > > I have had a problem report from a Recoll user about the amount of writes > > during index creation. > > > > https://opensourceprojects.eu/p/recoll1/tickets/67/ > > > > The issue is that the index is on SSD and that the amount of writes is > >