From: sgoldman@tower-research.com (Steve Goldman)
Subject: [sup-talk] Can sup only "save threads" on exit??
Date: Tue, 04 Nov 2008 17:55:57 -0500 [thread overview]
Message-ID: <1225839289-sup-7273@sgoldmanlinux.tower-research.com> (raw)
When I quit, sup goes through a slow process where it "saves" all the
modified threads. This is problematic because 1) it takes a long
time, and 2) if sup crashes before I get a chance to exit, then I have
to rearchive everything again.
Thanks.
--
Steve Goldman
sgoldman at tower-research.com
T: 212.219.6014
F: 212.219.6007
Tower Research Capital, LLC
377 Broadway, 11th Fl.
New York, NY 10013
next reply other threads:[~2008-11-04 22:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 22:55 Steve Goldman [this message]
2008-11-05 0:36 ` John Bent
2008-11-05 13:06 ` Nicolas Pouillard
2008-11-06 16:19 ` William Morgan
2008-11-07 14:18 ` Nicolas Pouillard
2008-11-10 4:49 ` William Morgan
2008-11-05 14:34 ` Steve Goldman
2008-11-05 17:59 ` William Morgan
2008-11-06 14:38 ` Steve Goldman
2008-11-06 16:18 ` William Morgan
2008-11-06 14:40 ` Nicolas Pouillard
2008-11-06 15:00 ` [sup-talk] [PATCH] save contacts.txt on '$' Nicolas Pouillard
2008-11-10 4:51 ` William Morgan
2008-11-06 22:35 ` [sup-talk] Can sup only "save threads" on exit?? William Morgan
2008-11-07 17:13 ` Mike Stipicevic
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=1225839289-sup-7273@sgoldmanlinux.tower-research.com \
--to=sgoldman@tower-research.com \
/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