Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Marc Seibert <sup@maseinet.de>
To: sup-talk@rubyforge.org
Subject: [sup-talk] run sup (or sup-sync) as daemon Hello everybody,
Date: Fri, 03 Dec 2010 01:41:22 +0100	[thread overview]
Message-ID: <1291336288-sup-8394@maseinet.de> (raw)

I am very new in using sup - and I am glad to find this nice tool for my console :-)
So I wonder if its a good idea to remove my procmail rules and manage the whole thing in ruby over sup.
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.
For this I have to write a script, that checks if there is a sup lock or not.
I just want too know, if there is a better solution.

Regards
Marc
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


             reply	other threads:[~2010-12-03  1:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03  0:41 Marc Seibert [this message]
2010-12-03  5:52 ` Tero Tilus
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=1291336288-sup-8394@maseinet.de \
    --to=sup@maseinet.de \
    --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