https://hackepedia.org/index.php?action=history&feed=atom&title=Pflogd 2026-05-08T16:32:07Z Revision history for this page on the wiki MediaWiki 1.45.3 https://hackepedia.org/index.php?title=Pflogd&diff=3520&oldid=prev 2007-02-23T19:13:40Z

<p>New page: # ps auwx | grep pflog root 19229 0.0 0.3 5016 1432 ?? Is 10:56AM 0:00.01 pflogd: [priv] (pflogd) _pflogd 19230 0.0 0.3 5080 1464 ?? S 10:56AM 0:...</p> <p><b>New page</b></p><div> # ps auwx | grep pflog<br /> root 19229 0.0 0.3 5016 1432 ?? Is 10:56AM 0:00.01 pflogd: [priv] (pflogd)<br /> _pflogd 19230 0.0 0.3 5080 1464 ?? S 10:56AM 0:00.06 pflogd: [suspended] -s 116 -f /var/log/pflog (pflogd)<br /> <br /> As you can see, I had pflogd suspended for some reason.<br /> <br /> from pflogd(8):<br /> <br /> pflogd tries to preserve the integrity of the log file against I/O<br /> errors. Furthermore, integrity of an existing log file is verified<br /> before appending. If there is an invalid log file or an I/O error, log-<br /> ging is suspended until a SIGHUP or a SIGALRM is received.<br /> <br /> <br /> I tried <br /> <br /> # pkill -HUP pflogd<br /> <br /> but no luck, it was still suspended. <br /> <br /> # /etc/rc.d/pflog stop<br /> # mv /var/log/pflog /var/log/pflog.fscked<br /> # touch /var/log/pflog<br /> # chmod 600 /var/log/pflog<br /> # /etc/rc.d/pflog start<br /> <br /> and I was back in the running:<br /> # ps auwx | grep pflog<br /> root 19406 0.0 0.3 5016 1432 ?? Is 11:07AM 0:00.01 pflogd: [priv] (pflogd)<br /> _pflogd 19407 0.0 0.3 5080 1456 ?? S 11:07AM 0:00.03 pflogd: [running] -s 116 -f /var/log/pflog (pflogd)</div>

Franks