The Following User Says Thank You to imhavoc For This Useful Post: | ||
|
2009-03-20
, 23:19
|
|
Posts: 109 |
Thanked: 37 times |
Joined on Oct 2008
@ NYC, NY
|
#2
|
To put your alarms on hold, open a shell:
cd /var/lib/alarmd
sudo mv alarm_queue.xml alarm_queue.xml.hold
....
Have a great vacation!
The Following User Says Thank You to fattomm For This Useful Post: | ||
|
2009-03-20
, 23:24
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#3
|
|
2009-03-20
, 23:32
|
|
Posts: 109 |
Thanked: 37 times |
Joined on Oct 2008
@ NYC, NY
|
#4
|
|
2009-03-21
, 16:20
|
Posts: 17 |
Thanked: 2 times |
Joined on Apr 2008
|
#5
|
|
2009-03-23
, 13:03
|
Posts: 631 |
Thanked: 837 times |
Joined on May 2007
@ Milton, Ontario, Canada
|
#6
|
Tags |
alarmd, alarms, vacation |
|
Here's what I learned during Christmas break:
To put your alarms on hold, open a shell:
cd /var/lib/alarmd
sudo mv alarm_queue.xml alarm_queue.xml.hold
reboot.
When you're ready to turn the alarms back on:
cd /var/lib/alarmd
sudo mv alarm_queue.xml.hold alarm_queue.xml
Be careful, though. If the file permissions get changed, you might not be able to change alarms later. Moving the file to ...hold rather than copying the file away and back helps to insure that the file permissions don't get changed.
Have a great vacation!