Due to a bug in init file, kresd is currently restarted every 10 minutes (I’m not certain if every Omnia gets caught into this loop).
Ehm, I guess that fixing the PID file by hand once should work around that cycle, at least until some other reason leads to restarting the service. (Far from ideal workaround.)
Yes. It’s supposed to contain the PID of the kresd process (a single number). I’m not certain the first one is always the correct one and not the other way around. pidof kresd > /tmp/run/resolver.pid will most likely work. (Though it’s exactly how the mistake happens, as multiple so-named processes exist during some init actions.)
I upgraded to 3.8.5 last night, made sure to disable kresd but looking at the system logs, it’s still reactivating itself and intefering with dnsmasq-full.
Is there anyway to disable kresd entirely (stopping short of uninstalling it)? Is anyone else experiecing this as of 3.8.5?
EDIT: For now, I’m resorted to setting a cron job that runs every three minutes to stop kresd when it spawns. So far so good but ultimately, this is just a stop-gap fix until I can find something more concrete.