From: Tero Tilus <tero@tilus.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] run sup (or sup-sync) as daemon Hello everybody,
Date: Fri, 03 Dec 2010 07:52:24 +0200 [thread overview]
Message-ID: <1291354461-sup-2909@tilus.net> (raw)
In-Reply-To: <1291336288-sup-8394@maseinet.de>
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
next prev parent reply other threads:[~2010-12-03 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 0:41 Marc Seibert
2010-12-03 5:52 ` Tero Tilus [this message]
2010-12-03 13:33 ` Mark Alexander
2010-12-03 14:16 ` Marc Seibert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1291354461-sup-2909@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox