CLOCKWORKD(1)
β¨ CLOCKWORKD β¨
okay bestie, welcome to the clockworkd page β it lives in the clockwork manual and honestly? it's giving little daemon that could π
πΈ NAME πΈ
clockworkd β the daemon that runs your clockwork scripts, no cap. Like, it just executes them, in the background, forever, like a lil guy doing cardio πβοΈ
π¦ SYNOPSIS π¦
clockworkd [-c FILE] [OPTIONS] {start|stop|restart|run}
so you pass it a file if you want, some options if you want, and then you tell it one of four words: start, stop, restart, or run. that's the whole vibe check. pick one. π
π DESCRIPTION π
clockworkd executes clockwork script as a daemon. that's it, that's the job, and it slays at it β¨
but listen β you will need the daemons gem to use clockworkd. it is not automatically installed. please install it by yourself, bestie, nobody's gonna do it for you π it's a whole DIY moment.
π OPTIONS π
okay this is the part where you actually read, because there's a lot and every single one matters π«Ά
--pid-dir=DIRβ alternate directory in which to store the process ids. the default isGEM_LOCATION/tmp. so like, if you wanna put your pids somewhere else, this is your girl π-i,--identifier=STRβ an identifier for the process. default is the clock file name. it's basically a little name tag for your process π·οΈ-l,--logβ redirect bothSTDOUTandSTDERRto a logfile namedclockworkd[.identifier].outputin the pid-file directory. yes both. everything. into the log. π--log-dir=DIRβ a specific directory to put the log files into. default location is the pid directory. so if you don't say anything, logs go hang out with the pids π-m,--monitorβ start monitor process. it's watching π iconic behaviour honestly-c,--clock=FILEβ clock.rbfile. default isGEM_LOCATION/clock.rb. that's your actual script, your main character π-d,--dir=DIRβ directory to change to once the process starts. like, the process gets a new home π-h,--helpβ show help message. the classic. the people's option π
π BUGS π
found a bug? bestie, please create an issue at https://github.com/tomykaira/clockwork/issues. we wanna know. spill. π«Ά
and if it's a bug fix or a feature request, please send a pull-request. but do not forget to add tests to show how your feature works, or what bug is fixed. no test, no vibe. and here's the thing: all existing tests and new tests must pass. TravisCI is watching ποΈπποΈ it sees everything. it's literally always watching.
π AUTHORS π
- Created by Adam Wiggins. π«‘
- Inspired by
rufus-schedulerandresque-scheduler. π‘ - Design assistance from Peter van Hardenberg and Matthew Soldo. π¨
- Patches contributed by Mark McGranaghan and LukΓ‘Ε‘ KonarovskΓ½. π©Ή
collab of the century fr fr.
π SEE ALSO π
https://github.com/tomykaira/clockwork. go look. go read. go click. β¨
and that's the whole page, babes β this one shipped as a Ruby Gem back in August 2014, and it's still out here executing clockwork scripts as a daemon. periodt. π ππ¦
π¦ where this page comes from
- debian bookworm: ruby-clockwork 3.0.1-1 Β· MIT
- debian trixie: ruby-clockwork 3.0.1-2 Β· MIT
- ubuntu jammy: ruby-clockwork 2.0.4-2 Β· MIT
- ubuntu noble: ruby-clockwork 3.0.1-1 Β· MIT
- ubuntu resolute: ruby-clockwork 3.0.1-2 Β· MIT
- ubuntu stonking: ruby-clockwork 4.0.1-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms