From owner-freebsd-questions@freebsd.org Thu Dec 22 05:53:31 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 511E1C8CCD6 for ; Thu, 22 Dec 2016 05:53:31 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 38BDE11C8 for ; Thu, 22 Dec 2016 05:53:31 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id BDA8211022A for ; Wed, 21 Dec 2016 23:53:29 -0600 (CST) Received: by mail.geeks.org (Postfix, from userid 1003) id 960EC110229; Wed, 21 Dec 2016 23:53:29 -0600 (CST) Date: Wed, 21 Dec 2016 23:53:29 -0600 From: Doug McIntyre To: freebsd-questions@freebsd.org Subject: mandoc.db keeps changing in 11.0-RELEASE? Message-ID: <20161222055329.GA81847@geeks.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.7.1 (2016-10-04) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2016 05:53:31 -0000 I've seen this happen on several FreeBSD 11.0-RELEASE systems I run. I have 'freebsd-update cron' running each night. And from time to time, I'll get a whole slew of notices about mandoc.db changing. Ie. this system is already at 11.0-RELEASE-p5.. $ freebsd-version 11.0-RELEASE-p5 And for a notice I get via email.. Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 11.0-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files will be updated as part of updating to 11.0-RELEASE-p5: /usr/share/man/mandoc.db /usr/share/openssl/man/mandoc.db And of course, I could ignore it, and each night it'll bug me, or I can update it with 'freebsd-update install', and the notice goes away. So, what's up with the 11.0 build process that mandoc.db keeps getting touched or whatever it is? This happens on most of my 11.0-RELEASE machines from time to time.