Christian Schwarz

> The cron lib doc says @daily means midnight ("0 0 * * *") - so it's different then anacron/cron in Linux. I don't think these @ "descriptors" are very...

One thing that came to mind though: People might want to use `cron` to implement a snapshot management scheme where they have separate "trains" of snapshots. Say, one cron that...

The last commits implements multiple cron schedules in one job. Try it with ``` - type: snap name: snapper filesystems: { "p1": true } snapshotting: type: cron schedules: - cron:...

Yeah, something along those lines. But I don't want to let this scope-creep too much. I imagine what I posted in https://github.com/zrepl/zrepl/pull/614#issuecomment-1190692441 would be a net improvement for many people...

One other things where I'm not sure what the best thing to do is: If two schedules fire at the same time, should we serialize the snapshotting, have it run...

> What's the downsize or impact of serializing snapshots? None, really, I think.

I'm thinking of backing out the multi-schedules change though. The same can be achieved with multiple `snap` jobs: ``` - type: snap name: snapper filesystems: { "p1": true } snapshotting:...

@spi43984 @khenderick please comment on whether the simple variant with only one schedule would be sufficient for you, given the considerations above.

Thank you for reaching out! and sorry for the delay, I am quite busy with my master thesis at the moment. > We would like to explicitly support zrepl and...

@InsanePrawn @infisil any chance you can take a look / test drive this? For my setup (which doesn't use unencrypted raw sends) I can confirm there have been no crashes...