From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Shared distfiles directory between different virtual machines
Date: Wed, 6 Nov 2024 18:34:01 -0600 [thread overview]
Message-ID: <59fae81f-2ec0-4b1c-9317-e0c76f11085e@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <3b23ce99-ad20-4131-be2a-47df87708e2c@paraboletancza.org>
On 11/6/24 11:39, whiteman808 wrote:
> What in case when two lock files are being created at the same time? How
> can I prevent in this case emerge fail?
Have you actually experienced this type of failure?
Or are you just thinking about worst case?
I've been sharing distfiles between multiple systems over NFS for years
and not had a problem. Granted, usually the systems aren't emerging at
the same time.
--
Grant. . . .
prev parent reply other threads:[~2024-11-07 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 17:16 [gentoo-user] Shared distfiles directory between different virtual machines whiteman808
2024-11-06 17:24 ` [gentoo-user] " Holger Hoffstätte
2024-11-06 17:39 ` whiteman808
2024-11-06 17:53 ` Filip Kobierski
2024-11-07 0:34 ` Grant Taylor [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=59fae81f-2ec0-4b1c-9317-e0c76f11085e@spamtrap.tnetconsulting.net \
--to=gtaylor@gentoo.tnetconsulting.net \
--cc=gentoo-user@lists.gentoo.org \
/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