------- cpufreqd1 ---------

- clarify manpages about rule matching (not the first rule but the highest score rule is applied)

- use the delay_cycles information to delay rule application

- use cpu_nice_scale to scale as per user preference

------- cpufreqd2 ---------

- execute program after policy switch

- selective resource to poll

- maintain the previous system read and check for differences, 
  if different trigger an new rule scan
  Maybe not possible because of running programs check (hummmm...)

- write a better search algorithm for running processes search
  ideas:
  - use a data structure other than linked list with faster access (hashtable / search tree?)
  - remove duplicates entries
  - remove sorting in reading /proc entries
  - use the exe link instead of cmd

- renice the process at a low priority when running on battery and at
  low frequencies

