triotactical.blogg.se

1. SET ALARM TIME ON DCLOCK LINUX HOW TO
2. SET ALARM TIME ON DCLOCK LINUX DRIVER
3. SET ALARM TIME ON DCLOCK LINUX PORTABLE
4. SET ALARM TIME ON DCLOCK LINUX CODE
5. SET ALARM TIME ON DCLOCK LINUX PLUS

Void (*callbackFunc)(void*), void *callbackArgs) I wonder why the behavior is different? The timer does work and happily chugs along it just doesn't see the system clock changes. I seem to be making all of the same function calls as LordHunter's examples. The callback() function exits the program.

SET ALARM TIME ON DCLOCK LINUX DRIVER

The test driver sets a timer for one day in the future and then checks the timer's status every second there after. I tried both of LordHunter's examples (had to tweak the threaded version to compiled on RHEL4) and they both are sensitive to changes in the system clock.īelow is my code. Signal delivery is probably "safer" and more portable, but we're talking about the difference between putting your finger underneath a 6000RPM saw and a 4000RPM saw, honestly.ĭown this path lies madness (or alcoholism) no matter what. Actual behavior will be highly implementation dependent, if it works at all (SIGEV_THREAD is probably not functional on a wide scale). Pthread's relationship with signal handling is grossly underdefined, and this is one of these cases.

Ignore the warning, AFAICT Linux defines the structure wrong (big surprise there). Struct timespec set = Pay close attention to the comments.

SET ALARM TIME ON DCLOCK LINUX CODE

This code seems to do what you want, tested using date - View image here: - : #include Why would using date to set the system clock time be unsafe?

SET ALARM TIME ON DCLOCK LINUX PORTABLE

I'll drop a link here if I can get it to work and end up posting it.AFAIK, the portable way is to do it yourself: sleep for a short period, check the current time against your previous time, and sleep again if necessary. I might actually write a script system for this and post it for clout, because now you've got me interested.

Setup a per-minute cronjob for alarm-start

SET ALARM TIME ON DCLOCK LINUX PLUS

var/last-alarm, before erasing it could also use the same file, but would need a different line format, plus adjustments to sorting in set-alarm) snoozing (would require an adjustment to alarm-start to dump the read alarm line to a separate file, e.g. Optional: add scripts for other alarm-related tasks, e.g. Optional: roll these together into different modes of operation for a master script, e.g. usr/local/bin/alarm-stop, that kills the audio player usr/local/bin/alarm-start, that checks next-alarm, and, if it's due (determined by checking against current time), runs cancel-next-alarm to clean it out of the alarms file, shows a notification somehow - say, notify-send from libnotify, for example - and plays the alarm audio

usr/local/bin/cancel-next-alarm, that just erases the first line of the alarms file, or does nothing if empty usr/local/bin/next-alarm, that just shows you the first line of the alarms file, or nothing if empty usr/local/bin/set-alarm, that can take a time of day, an alarm label / message, and an audio file path, concat them, read the alarms file, append the line to the file in memory, sort the lines from soonest alarm to farthest-future alarm, and dump the sorted file back to disk with the added line var/alarms (/var is appropriate because this file's contents will be temporary and change frequently) I don't know of any readily available solutions either, but this is what I'd do:Ĭreate an empty file e.g. This must be a really common thing, right?īecause most of my research is pulling up tons of people saying the same thing, that there's no good solution for an alarm clock, and some people have written very basic scripts and admitted it's not very good.

SET ALARM TIME ON DCLOCK LINUX HOW TO

I'm also confused why I can't find any information about how to incorporate or link an alarm type applet to polybar to see when pending alarms are set, or maybe even just to cancel or set an alarm optionally on polybar instead of or in addition to CLI. Even just the ability to enter something like alarm 8:03PM to set the alarm, and alarm -R or something similar to cancel it. I'd like a little more functionality than that though. I've found other random scripts but again anything using the terminal seems to require me to enter exactly how many minutes or seconds I want to wait. Do I need to keep the terminal open, and closing or Ctrl + c would exit the script? Regardless it doesn't seem like the best way. Also I'm new to linux but I'm finding mixed results about how easy/reliable it is to cancel a pending script running that way. I'm not picky, just would like to figure something out.Ī lot of people talk about using sleep with mplayer, but you need to enter the number of seconds or hours manually and can't enter a time. I'm running Arch Linux and am really struggling to find a decent alarm clock solution.