Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1
  • Unfortunately, the above workaround didn't actually work. After the modification to the crontab, I both restarted and did a (power off + power on), but found the "systemd-udevd" process to still running at a near 100% CPU usage. I even wrote the systemctl start and systemctl stop commands separately with the @reboot directive in the crontab, but even that failed. Commented Aug 10, 2019 at 5:16