View Single Post
Posts: 187 | Thanked: 345 times | Joined on Nov 2009
#357
Originally Posted by tetris11_ View Post
Does anyone know where the Alarmed config file is, or how to access the dbus alarm config?

I think the solution may lie there.
Does this occur with all events you delete or just some?

From the front page:

If it should happen that you create an event and for some reason it gets lost from Alarmed's menu/list, but still exists and acts, look in /var/cache/alarmd/alarm_queue.ini and you'll find your event somewhere at the bottom. It comes with a "cookie", which identifies it. For example: "cookie: 886". You can then use the CLI interface to delete the event. It will tell you it doesn't exist, but it will nevertheless delete the backend-event:
Code:
Code:
/opt/alarmed/alarmed.py -CD 886
__________________
Author of:
  • The "Alarmed" scheduling and automation app. (Supports alarms, switching profiles, resetting the GPRS counter, setting custom commands to go off, cron syntax and much more. GUI and CLI).
  • "Reaction face-off", a two-player puzzle/knowledge/reaction game.
  • "ytcli", a simple but effective command line youtube client which allows you to play videos from the CLI instantly or download videos on a queue.
 

The Following 3 Users Say Thank You to shapeshifter For This Useful Post: