Jeffrey Ratcliffe <jeffrey.ratcli...@gmail.com> writes: > Hi Łukasz, > > 2010/9/20 Łukasz Pankowski <lukp...@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..?
No, only if you set two alarms at 6.00 they both start at 6.00 and my schedule the next alarms two times. > >> 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 > way? > > Regards > > Jeff _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community