[Shr-User] [SHR-T] ffalarms

Jeffrey Ratcliffe jeffrey.ratcliffe at gmail.com
Mon Sep 20 14:30:32 CEST 2010

Hi Łukasz,

2010/9/20 Łukasz Pankowski <lukpank at o2.pl>:
> I, as the author of ffalarms see it too :), but as no one complains I
> can live with it.  The problem is that at the moment if you set multiple

Well, it *is* rather annoying.

> alarms at the same time they all schedule new alarms and due to race
> condition between them you end up with single alarm scheduled multiple
> times.  The simultaneous alarm processes try to own a dbus name, so only

Are you saying that if I want to schedule new alarms, at say, 6.00,
6.05, and 6.10, then I should create 6.00, quit and restart ffalarms,
create 6.05, etc..?

> List of alarms:
> ffalarms -l
> (see http://ffalarms.projects.openmoko.org/#command-line-options)
> or simply
> ls /var/spoolt/at

Right. That shows lots of duplicates scheduled, although the 3 alarms
I would like are correctly defined. To fix things, should I just
delete the duplicate scripts in /var/spool/at? or is there a better



More information about the community mailing list