On 10/1/24 11:29, Rodney W. Grimes wrote:
On 9/30/24 19:36, Jamie Landeg-Jones wrote:
Kyle Evans wrote:
It might be that the better long-term approach is to teach updatedb.sh
how to drop privileges and push that out of the periodic script to avoid
surprises like this from the different execut
> On 9/30/24 19:36, Jamie Landeg-Jones wrote:
> > Kyle Evans wrote:
> >
> >> It might be that the better long-term approach is to teach updatedb.sh
> >> how to drop privileges and push that out of the periodic script to avoid
> >> surprises like this from the different execution environments. Th
> Yes, my proposal is that it stops doing that and we teach updatedb to
> handle the priv-dropping instead, so that you get the same behavior no
> matter how you execute it.
Please don't, or at least don't without an option to avoid that. Having a
files DB for some projects is really handy, an
Konstantin Belousov wrote:
> On Tue, Oct 01, 2024 at 11:53:33AM +0300, Konstantin Belousov wrote:
>> On Tue, Oct 01, 2024 at 01:16:31PM +0700, dsdq...@hotmail.com wrote:
>>> Hyper-V Gen2 VM, 8 cores, 8GB RAM. The panic is reproducible while
>>> running `make -j8 buildworld`. Initially installed f
On Tue, Oct 01, 2024 at 11:53:33AM +0300, Konstantin Belousov wrote:
> On Tue, Oct 01, 2024 at 01:16:31PM +0700, dsdq...@hotmail.com wrote:
> > Hyper-V Gen2 VM, 8 cores, 8GB RAM. The panic is reproducible while
> > running `make -j8 buildworld`. Initially installed from
> > FreeBSD-15.0-CURRENT-a
On Mon, 30 Sep 2024, at 22:32, Kyle Evans wrote:
> - install $tmp $FCODES
> + cat $tmp > $FCODES
thank you!
--
On Tue, Oct 01, 2024 at 01:16:31PM +0700, dsdq...@hotmail.com wrote:
> Hyper-V Gen2 VM, 8 cores, 8GB RAM. The panic is reproducible while
> running `make -j8 buildworld`. Initially installed from
> FreeBSD-15.0-CURRENT-amd64-20240926-6a4f0c063718-272495-disc1.iso,
> updating the kernel (that I co
Kyle Evans wrote:
> Yes, my proposal is that it stops doing that and we teach updatedb to
> handle the priv-dropping instead, so that you get the same behavior no
> matter how you execute it.
Ahhh OK, I get you now. sorry, I musunderstood, I thought you meant the
current "periodic" method runs
On Sun, Sep 29, 2024 at 09:42:17AM -0700, Simon J. Gerraty wrote:
S> Michael Butler wrote:
S> > > I have found that *only* on arm64, locate errors like so:
S> > >
S> > > # sh /etc/periodic/weekly/310.locate
S>
S> This runs /usr/libexec/locate.updatedb as nobody
S> and ensures that /var/db/locate.
On 01/10/2024 03:21, Graham Perrin wrote:
Has anything changed in the past two months that might cause wake to
become unreliable?
… IIRC the unreliability became noticeable not long after the bump to
1500023. That was around the end of August (with pkgbase). …
Correction: that was, around
10 matches
Mail list logo
