It's Spring Break, and I'm ready to not have the alarm ringing at 5:30 a.m. every morning (and 6:25, and 6:50 and....).

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!

How about just a "sudo /etc/init.d/alarmd stop"? You can
avoid monkeying with permissions, etc -- and could maybe
even tie this to a button ... (so you could turn it off for weekends,
too ! :-))

The toggling is left as an exercise for the reader ....

I assume it's start to get it working again?

Yeah -- take a prowl around /etc/init.d -- most/all of the system services are started from there. Those are just shell scripts -- they're readable, and a few services implement more than start/stop ....

My tablet inevitably gets accidentally restarted during a week that I have free time to mess around with it. This prevents the alarms from restarting after a late-night reboot. Yours is better, mine is "failsafe."

Or just forgo the native alarm clock app and use FlipClock, which lets you set alarms that are triggered by AlarmD, but also gives you the ability to just turn them on and off (without having to muck around at the shell level, delete/re-enter them, etc):
https://garage.maemo.org/projects/flipclock/
It's also available from the extras-devel repository (will pull in dependencies automatically if you install from there).

It requires Python2.5, PyGame, and python2.5-gstreamer packages to work (it's not in extras yet so unfortunately dependencies can't be automatically pulled in), but if you haven't got these already it's just a matter of red pill/apt-get commands.