Date: Wed, 6 Feb 2013 19:00:37 +0100 From: Polytropon <freebsd@edvax.de> To: Tim Gustafson <tjg@ucsc.edu> Cc: questions@freebsd.org Subject: Re: Restricting Periodic Scripts Message-ID: <20130206190037.b72b64f5.freebsd@edvax.de> In-Reply-To: <CAPyBAS6vna0xMYbPR05PpFbMOJHJ613b%2BYJGhi9n-8kvfZP9JQ@mail.gmail.com> References: <CAPyBAS6tFC-LCKAzMMeq4nxkqJsD29tRTF=k7cAyUTFhkiKFCQ@mail.gmail.com> <CAPyBAS6vna0xMYbPR05PpFbMOJHJ613b%2BYJGhi9n-8kvfZP9JQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 6 Feb 2013 09:26:17 -0800, Tim Gustafson wrote: > I have a FreeBSD ZFS file server with tens of millions of files stored on it. > > But, the daily periodic scripts like > /etc/periodic/security/110.neggrpperm and > /etc/periodic/weekly/310.locate take hours iterating through those > folders, and I just don't need them to be scanned. > > I see that I can edit /etc/locate.rc to fix the behavior for > /etc/periodic/weekly/310.locate but I don't see a way to exclude > folders from other scripts like /etc/periodic/security/110.neggrpperm > from scanning them. Is there any way to prune out folders that I > don't want scanned, or should I just disable those jobs? You can disable them per /etc/periodic.conf (see examples in /etc/defaults/periodic.conf). To keep the functionality, but restrict it to a smaller amount of files, you could use the system's scripts as templates, make your own "derivates" (wich inclusion or exclusion rules) and place them in /usr/local/etc/periodic for the system to call them (which it will if they are present). You can add your custom configuration flags to /etc/periodic.conf and have your scripts source that file (like the system's scripts do). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130206190037.b72b64f5.freebsd>