User:Magick777/My N900 Scheduling
(→Backups) |
(→Criteria for scheduling events) |
||
Line 22: | Line 22: | ||
Certain actions need to be scheduled according to time of day, week or month, i.e. as per the scheduling behaviour of the Unix cron daemon. There seem to be two viable ways of achieving this, via [[fcron]] and [http://talk.maemo.org/showthread.php?t=46594 Alarmed]. The [fcron] page is well-written and useful, but I think [http://talk.maemo.org/showthread.php?t=46594 Alarmed] is the better tool for the job, partly on the strength of the GUI and partly because it uses an existing daemon rather than adding another one. | Certain actions need to be scheduled according to time of day, week or month, i.e. as per the scheduling behaviour of the Unix cron daemon. There seem to be two viable ways of achieving this, via [[fcron]] and [http://talk.maemo.org/showthread.php?t=46594 Alarmed]. The [fcron] page is well-written and useful, but I think [http://talk.maemo.org/showthread.php?t=46594 Alarmed] is the better tool for the job, partly on the strength of the GUI and partly because it uses an existing daemon rather than adding another one. | ||
+ | |||
+ | == Phone status & event scheduling == | ||
- | |||
== Calendar-based scheduling == | == Calendar-based scheduling == | ||
== Location-based scheduling == | == Location-based scheduling == | ||
+ | |||
+ | * When not at home, turn WiFi off unless and until explicitly requested | ||
+ | * When at home, turn WiFi on and autoconnect | ||
= Changelog for scheduled events = | = Changelog for scheduled events = |
Revision as of 17:25, 15 July 2010
Contents |
Approaches to scheduling
fcron
alarmed
What do I need to schedule
Backups
- Regular backups can be scheduled from alarmed at such time as I have a suitable backup script.
Maintenance
- Reset data counters, monthly (done via Alarmed)
Profiles
Criteria for scheduling events
Cron-based scheduling
Certain actions need to be scheduled according to time of day, week or month, i.e. as per the scheduling behaviour of the Unix cron daemon. There seem to be two viable ways of achieving this, via fcron and Alarmed. The [fcron] page is well-written and useful, but I think Alarmed is the better tool for the job, partly on the strength of the GUI and partly because it uses an existing daemon rather than adding another one.
Phone status & event scheduling
Calendar-based scheduling
Location-based scheduling
- When not at home, turn WiFi off unless and until explicitly requested
- When at home, turn WiFi on and autoconnect
Changelog for scheduled events
This will be moved to the bottom of the page later.
2010-07-15
- Installed 'alarmed' from extras-devel, had to ln -sf python2.5 to /usr/bin/python
- Configured alarmed to reset GPRS data at 0000 on 1st of each month