Fred

Thank you for your detailed description. The problem is because I'm using `alpine` Linux as a base image. I'm going to try if it works with adding the package [busybox-suid](https://pkgs.alpinelinux.org/package/edge/main/x86/busybox-suid)....

So, in the end I didn't like the idea of having suid on all the busybox binaries. I prepared a contribution based on supercronic instead. I'm now thinking of proposing...

> Note: I've removed the comment that V2 configs will disallow inline schedules since I think this limitation isn't required. After all inline schedules are the only option to inherit...

or maybe just moving all `schedule-*` options into a `scheduling` subsection, attached to a profile or a group. Maybe that would be nicer after all

~I can see there are still some broken links in the documentation since the latest version of Hugo 😞 Maybe I should just pin the version for now 🤔 that's...

> Agree that it all became too verbose with the `--verbose` flag enabled. Still I think changes to the env is an important log output. I've reduced unfiltered-log to trace...

Closing as not enough information. You can re-open if needed 👍🏻

Hi, Yes I see what you mean. This is something we can take into consideration when reviewing the version 2 of the configuration file format. In the meantime it's easy...

Hi, The reason it's not a tag expected on the profile configuration is because it's not a flag for some commands. All the flags at the root would be applied...

I didn't think it would be useful at the time, but now I can see how it can be in some cases. It's not a big change. In the meantime,...