Title: LFD errors
Last modified: June 14, 2017

---

# LFD errors

 *  [linkup](https://wordpress.org/support/users/linkup/)
 * (@linkup)
 * [9 years ago](https://wordpress.org/support/topic/lfd-errors/)
 * I know this was address in another topic, but I didn’t care for the bandaid support
   option that was given.
 * [https://wordpress.org/support/topic/help-with-csf-firewall-removing-lfd-process-check-for-wf/](https://wordpress.org/support/topic/help-with-csf-firewall-removing-lfd-process-check-for-wf/)
 * The suggestion was to tell CSF to ignore Wordfence. I don’t think the security
   of the server should have to be compromised so a plugin can work. Furthermore,
   making a user go into the root of their server to accomplish this. Most users
   won’t have access to root and most users when asking their host to make exceptions
   for their applications will be told to take a hike.
 * I am getting hundreds of errors caused by Wordfence and it seems the better solution
   might be to get rid of Wordfence for a product that doesn’t make you bypass security
   or make root level changes to accomplish that

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Thread Starter [linkup](https://wordpress.org/support/users/linkup/)
 * (@linkup)
 * [9 years ago](https://wordpress.org/support/topic/lfd-errors/#post-8984786)
 * I found through the CSF dashboard that you can modify the csf.pignore file to
   have it ignore what Wordfence is doing, but that topic, marked as resolved, never
   provided suggested lines to add to CSF.pignore? My hosts added a similar line
   for spamd, but that was a process, a cmd, not whatever it is that is causing 
   the constant LFD errors.
 * Anyone had to deal with this, anyone know what exclusions to add to the file?
 * Thanks
 *  [davert318](https://wordpress.org/support/users/davert318/)
 * (@davert318)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/lfd-errors/#post-9149193)
 * I am wondering the same.
 *  [Sean Michaud](https://wordpress.org/support/users/seismicpixels/)
 * (@seismicpixels)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/lfd-errors/#post-9198905)
 * Because the command line is wp-cron.php you’d either have to ignore something
   like
    cmd:/usr/bin/php /home/*/public_html/wp-cron.php (which is probably bad
   since it’ll stop notifications on every script running with wp-cron) OR check
   out the Uptime in your notifications and set PT_LIMIT to something higher. You
   may still get some notifications, but they’ll be a lot less.
 * CSF states the following with the PT_LIMIT:
    “The following is the number of 
   seconds a process has to be active before it is inspected. If you set this time
   too low, then you will likely trigger false-positives with CGI or PHP scripts.”
 *  [davert318](https://wordpress.org/support/users/davert318/)
 * (@davert318)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/lfd-errors/#post-9198951)
 * Thanks. That’s good to know — both parts!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘LFD errors’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [CSF](https://wordpress.org/support/topic-tag/csf/)

 * 5 replies
 * 3 participants
 * Last reply from: [linkup](https://wordpress.org/support/users/linkup/)
 * Last activity: [8 years, 10 months ago](https://wordpress.org/support/topic/lfd-errors/#post-9225590)
 * Status: not resolved