From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"ibr@radix50.net" <ibr@radix50.net>
Subject: Re: [PATCH v2 0/4] Fix ccache issues
Date: Mon, 10 Apr 2023 05:44:01 +0000 [thread overview]
Message-ID: <f421824432bb650382f34710c70296af74b859f4.camel@siemens.com> (raw)
In-Reply-To: <ZC13j/T+TWGtDlbn@ilbers.de>
On Wed, 2023-04-05 at 15:28 +0200, Baurzhan Ismagulov wrote:
> On 2023-04-05 11:56, Moessbauer, Felix wrote:
> > > What about sudo addgroup ccache; sudo adduser build ccache; sudo
> > > chgrp -R
> > > ccache /ccache; sudo chmod -R g+w /ccache; find /ccache -type d
> > > |sudo
> > > xargs
> > > chmod g+s? Maybe also sudo adduser root ccache.
> >
> > This would solve the permission issues at the cost of always
> > touching a
> > lot of files.
>
> Hmm, why always a lot? This is meant as a one-time action during
> setup. Set the
> directory group to ccache, set the mode to at least 2770 -- anything
> that is
> created under it should be readable and writable by anyone in the
> group. I used
> this in the past, but didn't test with root and NFS.
Is this a one-time action per dpkg-build task, or how often is that
called? I'm also a bit unsure how that works together with other ccache
instances from older ISAR versions that simultaneously work on the same
cache, but using root. The automatic internal cleanup logic of the
ccache as builder might then want to delete ccache entries which have
been created by a ccache running as root, but after the chmod:
An example sequence is the following (A: old, B:new):
B: run chmod
A: create cache entries
B: write to cache, fill it up and delete entries created by A
Do I miss something?
Best regards,
Felix
>
> With kind regards,
> Baurzhan
>
prev parent reply other threads:[~2023-04-10 5:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 7:56 Anton Mikanovich
2023-02-13 7:56 ` [PATCH v2 1/4] ccache: fix dirs creation Anton Mikanovich
2023-02-13 7:56 ` [PATCH v2 2/4] ccache: fix CCACHE_DIR owner for sbuild Anton Mikanovich
2023-02-13 7:56 ` [PATCH v2 3/4] meta: unify cross selection Anton Mikanovich
2023-02-13 7:56 ` [PATCH v2 4/4] ccache: separate cache based on cross compile Anton Mikanovich
2023-02-13 8:01 ` [PATCH v2 0/4] Fix ccache issues Anton Mikanovich
2023-03-27 5:27 ` Uladzimir Bely
2023-03-28 15:51 ` Moessbauer, Felix
2023-03-28 15:56 ` Uladzimir Bely
2023-03-29 12:43 ` Moessbauer, Felix
2023-03-30 7:37 ` Uladzimir Bely
2023-04-02 18:44 ` Baurzhan Ismagulov
2023-04-05 11:56 ` Moessbauer, Felix
2023-04-05 13:28 ` Baurzhan Ismagulov
2023-04-10 5:44 ` Moessbauer, Felix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f421824432bb650382f34710c70296af74b859f4.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox