Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
* [sup-talk] sup -c while sup is running?
       [not found] <1244646784-sup-7039@cabinet>
@ 2009-06-12 19:54 ` William Morgan
  0 siblings, 0 replies; only message in thread
From: William Morgan @ 2009-06-12 19:54 UTC (permalink / raw)


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>


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-06-12 19:54 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1244646784-sup-7039@cabinet>
2009-06-12 19:54 ` [sup-talk] sup -c while sup is running? William Morgan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox