Date: Sat, 15 Dec 2018 17:55:44 +0700 From: Eugene Grosbein <eugen@freebsd.org> To: Andre Albsmeier <Andre.Albsmeier@siemens.com> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org Subject: Re: svn commit: r341794 - stable/11/etc/periodic/weekly Message-ID: <c00a7e0c-5258-26b2-efea-72af490d71a1@freebsd.org> In-Reply-To: <20181215090926.GA33682@bali> References: <201812101424.wBAEOgbC053582@repo.freebsd.org> <20181215090926.GA33682@bali>
next in thread | previous in thread | raw e-mail | index | archive | help
15.12.2018 16:09, Andre Albsmeier wrote: > On Mon, 10-Dec-2018 at 14:24:42 +0000, Eugene Grosbein wrote: >> Author: eugen >> Date: Mon Dec 10 14:24:41 2018 >> New Revision: 341794 >> URL: https://svnweb.freebsd.org/changeset/base/341794 >> >> Log: >> MFC r340322-r340324,r340327: periodic/etc/weekly/340.noid >> >> Prevent periodic/etc/weekly/340.noid from descending into root directories >> of jails. Jails have their own user/group databases and this script >> can produce multiple false warnings, not to mention significant extra >> load in case of large jailed subtrees. Leave this check for jailed >> invocations of the same script. > > This gave me: > > Check for files with an unknown user or group: > .: cannot open /usr/share/bsdconfig/common.subr: No such file or directory > > on systems where bsdconfig is not installed. This periodic script does not try to access /usr/share/bsdconfig/common.subr I think error message comes from another periodic script. Can you please run it with "sh -x /etc/periodic/weekly/340.noid" to make sure?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c00a7e0c-5258-26b2-efea-72af490d71a1>