From: chrisw@rice.edu (Christopher Warrington)
Subject: [sup-talk] [PATCH] polling is now done per source
Date: Thu, 17 Apr 2008 17:24:35 -0500 [thread overview]
Message-ID: <1208470560-sup-9902@chris-tablet> (raw)
In-Reply-To: <1208465750-sup-5733@cabinet>
Excerpts from Marc Hartstein's message of Thu Apr 17 15:58:29 -0500 2008:
>> Each source has a poll_interval property. This property is used to
>> determine whether the source should be polled. The user can still
>> for a poll of all sources.
> Thanks for the patch. Seems to work great. Only one problem.
Well, there is another. The before-poll hook doesn't get the correct
arguments and before-acct-poll is run twice. I've fixed this locally
and will post a patch to the patch (or a unified path) once I figure
out how to do that in git.
> When this patch is applied and then sup is run against an old
> sources.yaml (which doesn't provide the poll_interval property), sup
> will crash on startup.
Hmmm... I don't know enough about the yaml infrastructure to fix
this. Does anyone else know if there is a way to specify a default
value when one if not found in the yaml file. This would allow for
graceful upgrading and (in theory) keep the sources.yaml file backward
compatible.
--
Christopher Warrington <chrisw at rice.edu>
next prev parent reply other threads:[~2008-04-17 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 0:22 [sup-talk] New User Questions Marc Hartstein
2008-03-28 10:33 ` Marcus Williams
2008-03-28 11:24 ` vasudeva
2008-03-28 17:23 ` Marc Hartstein
2008-03-28 19:51 ` Marcus Williams
2008-03-29 7:57 ` [sup-talk] [PATCH] polling is now done per source Christopher Warrington
2008-03-29 9:59 ` Christopher Warrington
2008-03-29 10:32 ` Christopher Warrington
2008-03-30 3:15 ` Christopher Warrington
2008-04-17 20:58 ` Marc Hartstein
2008-04-17 22:24 ` Christopher Warrington [this message]
2008-03-29 16:41 ` [sup-talk] Different Key Bindings (was: New User Questions) Guarded Identity
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=1208470560-sup-9902@chris-tablet \
--to=chrisw@rice.edu \
/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