From nobody Mon Sep 30 18:11:39 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XHTfl4WHHz5XSC7 for ; Mon, 30 Sep 2024 18:11:43 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XHTfl3xQxz4pnh; Mon, 30 Sep 2024 18:11:43 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727719903; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=dgFfJXHHvtOIUa5GxXDjUoQcAwgxyjA5QYNfxopaxH0=; b=KyJIeEhWKdNyazNFQPn/rzOymY6ZxgYjHg7MBwhWVYaGExZCdrx8UQWKmvo365ImfpO2BX Rzi3ZF82NvvUk4RzZmIrvTadikgMzizb5mhT8HpLsvIt3kJVNVcThGQSztLa9GazN/5MK+ NfgeWTkyLMfZ5V0NR1Pl3blUS2z0kkirjC2DQhYrw5yPAnqOJChAhMc/88iqKEjtZNxzDW xGeBP31EcJHRz0SciN5Zo/KGSfAOKNeV48BgvdTvWK/TH0TbNUwJbX/kv5HiD3CynBuNii Npi+KZHUvMzBChjVdbSYiGA9a5SKor5oQrAacjrVoamTtWoSQIr64iA7eGdfnA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727719903; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=dgFfJXHHvtOIUa5GxXDjUoQcAwgxyjA5QYNfxopaxH0=; b=j0DBsn11d6cmuWFzElq+KsLBTCxazGq/1rRAMDsGT4cMuCAe1QHk56yoASxsyOc6QxZnHv IklkZVeBThkvHBMrghZrYSNMpsK7JW4SAjISjkauOCperJ1ZLpWrevNahfl7Kol+f3PXx5 S7FUrsXpGKVxqlyJPO6wSnix4Y/liAn8I5MZQo3kuyFlTGC2Kzrm6tOnSAfiSsoupgrSo3 ZfEEG/+w0mg1smRaY9r5gULSENgSPdf6NMRxLCxWNYFkQ6TFZYHtM+IU9qZt5hJpkEmM4f 6afvju8+uDG6y5B+A1Igp1ROsWe+cdQ3dfY+O2mtVx2+x67+o5kiO99Ta9jlcQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727719903; a=rsa-sha256; cv=none; b=OuKvBWCkrXU7Oub6z7BhPrqc4k0GMQCXZxykNt62GWcZna2nmuWxhOaRWS0ESQ+A7gG9uD V74yYlrPf+ZYH7O7ep+F8MQ+Yh4wizsK3u9ddjuDW2uawNLaZA6nmKZ+zGMbrnlAzZzUyo d6TBXdFNpkpDlmXLP8nBm/lL/toiROdWkiJ27LhQfWYDmzzdLVCR8Bjxk9e/w+/POqiqOy f5U3nan/Ohu2iHAQPQSOwlp36fQwr6fm1qkjBANjNpJS8EOsf0RQJEqZCnUT6/dG0L9XKb EuZrvMjqMwXbfMVgiWNYtwQLTla0VuMHgcw5IH9ZcZz1qjvOI3htwoPXv/Qdjw== Received: from cell.glebi.us (glebi.us [162.251.186.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XHTfl0gyPzQCQ; Mon, 30 Sep 2024 18:11:42 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Mon, 30 Sep 2024 11:11:39 -0700 From: Gleb Smirnoff To: void , freebsd-current@freebsd.org Subject: weekly locate error Was: September 2024 stabilization week Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Sat, Sep 28, 2024 at 11:10:57PM +0100, void wrote: v> I have found that *only* on arm64, locate errors like so: v> v> # sh /etc/periodic/weekly/310.locate v> v> Rebuilding locate database: v> install: /var/db/INS@ArwCNx: Permission denied v> v> However, if it's run like this: v> v> # sh /usr/libexec/locate.updatedb v> > > > WARNING v> > > > Executing updatedb as root. This WILL reveal all filenames v> > > > on your machine to all login users, which is a security risk. v> v> it exits normally. v> v> Moving /var/db/locate.database aside makes no difference. The problem doesn't v> happen on amd64 arch, same 6e414739fc95. I also observe this and on amd64, so this is not arch specific. Not sure this appeared in the latest stabilization cycle, could have been introduced earlier. Manual run of the periodic job doesn't reproduce the problem :( -- Gleb Smirnoff