Our bundles have all the data, and therefore all the evidence. The
cronie package is only available in the
cronie bundle, and that is not part of any dependency or include. It doesn’t matter though, the error is still pretty annoying.
[quote=“ketonik, post:6, topic:1620”]
I don’t have
Entirely correct. That would be against our own packaging rules.
This isn’t a clearlinux problem. Logs are semi-anonymous and applications can spoof log messages. However, fortunately, you have really good evidence what software is making the error, because
crond is stating exactly which PID and process name is doing this.
With that information, you can run
systemd-cgls and see what unit/service this process belongs to. For instance, if I was looking on my system for something logging something like this:
NetworkManager: <info> [1568667028.7461] agent-m...
Then I can track it down through
systemd-cgls and see:
│ └─490 /usr/bin/NetworkManager --no-daemon
Then a simple
systemctl status NetworkManager.service tells me the rest of the information.
BTW, a simple
sudo mkdir /etc/cron.d will likely make the error disappear.