Re: periodic daily takes a very long time to run (14-stable)

On 27/10/23 17:07, Guido Falsi wrote:
> On 27/10/23 16:42, void wrote:
>> On Fri, Oct 27, 2023 at 03:34:35PM +0200, Ronald Klop wrote:
>>> So if my observation is right it might be interesting to find out 
>>> what is writing. 
>>
>> would ktrace and/or truss be useful? something else? The truss -p 
>> output of the
>> find PID produces massive amounts of output, all like this:
>>
>> fstatat(AT_FDCWD,"5e70d5f895ccc92af6a7d5226f818b-81464.o",{ 
>> mode=-rw-r--r-- ,inode=367004,size=10312,blksize=10752 
>> },AT_SYMLINK_NOFOLLOW) = 0 (0x0)
>>
>> with the filename changing each time
>>
>> (later...)
>>
>> that file is in ccache!!!
>>
>> locate 5e70d5f895ccc92af6a7d5226f818b-81464.o
>> /var/cache/ccache/f/5/5e70d5f895ccc92af6a7d5226f818b-81464.o
>>
>> maybe if I can exclude that dir (and /usr/obj) it'll lessen the 
>> periodic runtime.
>> But i don't know yet whats calling find(1) when periodic daily runs. 
>> If I can, I might be able to tell it not to walk certain heirarchies.
> 
> 
> I stumbled on a similar problem. Periodic trying to scan huge ccache 
> directories.
> 
> The script doing that was locate database indexing in weekly. Not sure 
> if you're having the same issue, but this could give you ideas.
> 
> My fix was:
> 
> weekly_locate_enable="YES"
> PRUNEPATHS="/tmp, /usr/tmp, /var/tmp, /var/db/portsnap, 
> /var/db/freebsd-update, /dumpster/ccache, /poudriere"
> 

Forgot to mention, this goes in /etc/periodic.conf.

-- 
Guido Falsi <mad@madpilot.net>