Kyle Evans wrote:
> This is the problem I have with mailing lists; 2/3 responses didn't go
> back and read the critical bit of context to my stance (but at least you
> still included it in your quote, the other one trimmed it entirely):
I quoted the part I was referring to. I trimmed the rest,
Hi Kyle,
> This is the problem I have with mailing lists;
This is not only a problem with mailing lists, but more generally with written
communication.
> 2/3 responses didn't go back and read the critical bit of context to my
> stance (but at least you
> still included it in your quote, the
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 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
On Mon, 30 Sep 2024, at 22:32, Kyle Evans wrote:
> - install $tmp $FCODES
> + cat $tmp > $FCODES
thank you!
--
> 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
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. This
/feels/ like the ki
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. This
> /feels/ like the kind of thing we could take an opinion
On 9/30/24 16:28, void wrote:
On Mon, Sep 30, 2024 at 02:08:18PM -0700, Gleb Smirnoff wrote:
M> > Manual run of the periodic job doesn't reproduce the problem :(
M>
M> Backing out commit f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9
resolves it for
M> me,
Sorry but I'm quite dense regarding git.
On Mon, Sep 30, 2024 at 02:08:18PM -0700, Gleb Smirnoff wrote:
M> > Manual run of the periodic job doesn't reproduce the problem :(
M>
M> Backing out commit f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9 resolves it for
M> me,
Sorry but I'm quite dense regarding git. Can you describe how exactly
wha
On Mon, Sep 30, 2024 at 02:25:49PM -0400, Michael Butler wrote:
M> On 9/30/24 14:11, Gleb Smirnoff wrote:
M> > On Sat, Sep 28, 2024 at 11:10:57PM +0100, void wrote:
M> > v> I have found that *only* on arm64, locate errors like so:
M> > v>
M> > v> # sh /etc/periodic/weekly/310.locate
M> > v>
M> > v>
On 9/30/24 14:11, Gleb Smirnoff wrote:
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, i
13 matches
Mail list logo
