From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs3516icb; Thu, 2 Dec 2010 22:16:15 -0800 (PST) Received: by 10.229.98.198 with SMTP id r6mr909802qcn.124.1291356974713; Thu, 02 Dec 2010 22:16:14 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id u29si3127268qcp.63.2010.12.02.22.16.14; Thu, 02 Dec 2010 22:16:14 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 2F66218582EE; Fri, 3 Dec 2010 01:16:14 -0500 (EST) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 0914418581F3 for ; Fri, 3 Dec 2010 00:52:24 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id 177076017; Fri, 3 Dec 2010 07:52:24 +0200 (EET) From: Tero Tilus To: sup-talk In-reply-to: <1291336288-sup-8394@maseinet.de> References: <1291336288-sup-8394@maseinet.de> Date: Fri, 03 Dec 2010 07:52:24 +0200 Message-Id: <1291354461-sup-2909@tilus.net> User-Agent: Sup/git Subject: Re: [sup-talk] run sup (or sup-sync) as daemon Hello everybody, X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Marc Seibert, 2010-12-03 02:41: > So I wonder if its a good idea to remove my procmail rules and > manage the whole thing in ruby over sup. I did exactly that. Hooks (especially before-add-message) are your best friends. > There is no daemon mode built in - if I got it right - so I want to > write a cron job to sup-sync every ten minutes. Why would you want to do that? When sup is running, it polls periodically for new mail. When its not, why would you care? You can think of sup-sync as parameterized way of doing what sup itself does when it polls for new mail (only from sources that are marked "usua", i.e. they are expected to receive new mail) and does indexing. Sup-sync comes handy when you start with sup and want to index all the sources or want to restore a dump. Other than that, sup maintains index by itself by polling on start and periodically after that. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk