the number of files mentioned before IS number of files the php scanner had scanned and reported.
Yes, I understood that. The number of files I reported (7262) is the total number of PHP files scanned on my dev site. The total number of files is nearly 20000.
The only thing that comes to mind is that you have one or more directories with several hundreds or thousands of files. This might cause bad performance, but still not 10 hours to scan a site. On top of that, you already told me that you excluded the directories with these files:
we are using jotcache which does produce large php cache files someimes, but as it was stated, PFS ignores these folders by default, and i think i added them (well just main cache folder not subfolders), to exclude listing as well.
I have noticed that two files are created when pfs is running in tmp directory where one is a tmp file, which i thought would pass details to main file to it would gradually increase in size, but they go up and down in size, so its not a gradual increase ( and no i dont do this everytime pfs runs, this was one off to see if it actually doing anything).
Is it a PHP file? I mean, does it have an extension which would cause the PHP File Change Scanner to scan it? If not, this is irrelevant. If it is a huge file and it is being scanned I would expect the scanner to hang, not stall for 8 hours.
I have an idea. The scanner takes a very long time when you're using the web to run it. Can you please try using a CRON job to run it and tell me how long it takes?
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!