Closed 3hhh closed 1 week ago
Why exactly do you expect it not running? It is a normal service that executes periodic system tasks, so it should be running.
There's even some Qubes OS specific stuff in /etc/cron.*/
This issue has been closed as "not applicable." Here are some common examples of cases in which issues are closed as not applicable:
We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.
Regarding help and support requests, please note that this issue tracker (qubes-issues) is not intended to serve as a help desk or tech support center. Instead, we've set up other venues where you can ask for help and support, ask questions, and have discussions. By contrast, the issue tracker is more of a technical tool intended to support our developers in their work. We thank you for your understanding.
If anyone reading this believes that this issue was closed in error or that the resolution of "not applicable" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.
On 9/4/24 10:57, Marek Marczykowski-Górecki wrote:
Why exactly do you expect it not running? It is a normal service that executes periodic system tasks, so it should be running.
Argh, I had confused it with cups, which I hadn't expected to be running, but it's not so it's all fine. Sorry for the fuzz, my bad...
How to file a helpful issue
Qubes OS release
4.2
Brief summary
crond runs in dom0
Steps to reproduce
systemctl status crond
in dom0Expected behavior
Not running.
Actual behavior
Running.