On Mon, 2022-06-27 at 09:11 -0500, Seebs wrote:
> On Mon, 27 Jun 2022 14:52:39 +0100
> Richard Purdie <[email protected]> wrote:
> 
> > b) We could add a new command to run an integrity check on the DB to
> > pseudo. If we do that, we would then be able to show the user a decent
> > error and above the timeout issue. The question is where/when to
> > trigger it and whether races could occur against the check (e.g. where
> > multiple fakeroot tasks are running in parallel against the same
> > WORKDIR).
> 
> I thought there was a function that did roughly this once at some point.

There is, triggered from a commandline option currently. I'm not sure
how well it would get on with a resident server in it's current form
but I've been using that function code in my experiments. The challenge
is how/when to trigger it.

Cheers,

Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#167324): 
https://lists.openembedded.org/g/openembedded-core/message/167324
Mute This Topic: https://lists.openembedded.org/mt/92020938/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to