Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup -c while sup is running?
Date: Fri, 12 Jun 2009 12:54:26 -0700	[thread overview]
Message-ID: <1244835514-sup-3886@entry> (raw)
In-Reply-To: <1244646784-sup-7039@cabinet>

Reformatted excerpts from Marc Hartstein's message of 2009-06-10:
> How difficult would it be to allow sup -c to be run while sup is
> already running?  The goal would be to be able to use sup as a mailto:
> handler effectively.

Not that difficult. In general, N Sup processes should be able to run as
long as N-1 of them are readonly wrt the index and sources file. (I
think!) So sup -c could launch either with a readonly inbox buffer, or
without one at all. (Which would be faster, if the intention is just to
quit after sending.)

However, to be safe, locking should be added to the sent.mbox to prevent
multiple Sup processing from overwriting each other's sent messages. Ben
Walton's lock manager I think will be perfect for this.
-- 
William <wmorgan-sup at masanjin.net>


           reply	other threads:[~2009-06-12 19:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1244646784-sup-7039@cabinet>]

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=1244835514-sup-3886@entry \
    --to=wmorgan-sup@masanjin.net \
    /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