3 Commits

Include renames

Author	SHA1	Message	Date
jochen	2dbbda51c6	Walk for setuid programs in the engine and carry an interrupted walk on (hq issue 361) ... The control-node's walk takes far longer than the engine runs between updates, so a search that starts over at every restart never completes. The walk is the engine's own, in lexical order, so its progress is one cursor per filesystem, kept every minute beside the engine's state and carried on after a restart while younger than rootsearch.FreshFor. It runs on a thread of its own at nice 19 and the idle I/O class.	2026-10-10 01:00:47 +02:00
jochen	2410796869	Let the setuid search run to completion and judge from the last complete one (hq issue 361) ... A machine with millions of files never finished the walk within fifteen minutes, so its agent account was never judged and the router refused to link. Only root can make a setuid-root file, so a complete search stays sound until root acts: it now runs at idle priority with no bound, is kept beside the engine's state, judges for rootsearch.FreshFor from its start, runs again daily and after an apply that moves accounts, packages, actions or sudo rules, and an incomplete or stale search is never free.	2026-10-10 00:53:05 +02:00
jochen	2673e7a2c9	Let the setuid search run to its 15-minute bound, ask pacman once, and call a walk with errors incomplete ... The search kept a two-minute limit of its own inside its 15-minute bound, so a long walk always ended incomplete; pacman was asked once per path; and find exiting with an error but some output was read as a complete walk. The bound and the not-judged reasons move to the public rootsearch package so the controller reads the same values (the review of 2026-10-09).	2026-10-09 12:11:57 +02:00