public inbox for gentoo-user-de@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user-de@lists.gentoo.org
Subject: Re: [gentoo-user-de] Re: distfiles mit NFS exportieren - kann keine Locks erzeugen :(
Date: Thu, 01 Sep 2005 15:37:48 +0200	[thread overview]
Message-ID: <4317042C.2070609@mid.email-server.info> (raw)
In-Reply-To: <2def88b8050822052164848087@mail.gmail.com>

Arnold Krille schrieb:
> On 8/22/05, Alexander Skwar <listen@alexander.skwar.name> wrote:
>> Aber stimmt schon, ich hätte noch den Server zeigen sollen.
>> In /etc/exports von dort:
>> /Gentoo/Portage/distfiles                      
>> *.bei.digitalprojects.com(async,rw,no_root_squash)
> 
> Versuch das mal mit sync (statt async), das hab ich bei allen meinen
> dirs und ich bekomme keine Probleme mit dem portage-over-nfs...

Ich habe inzwischen auf sync umgestellt - und es klappt
immer noch nicht :(

Warum erhalte ich wohl immer "Permission Denied"? Wer
verweigert hier wem die Erlaubnis - und vor allem: Warum?
Und noch wichtiger: Wie kann ich das ändern?


Hier nochmal die Fehlermeldung - ist ja schon 'n paar
Tage her...

alexander@blatt ~ $ sudo -H emerge -vat app-text/txt2man

These are the packages that I would merge, in reverse order:

Calculating dependencies ...done!
[ebuild  N    ] app-text/txt2man-1.4.8-r1  11 kB

Total size of downloads: 11 kB

Do you want me to merge these packages? [Yes/No]
>>> emerge (1 of 1) app-text/txt2man-1.4.8-r1 to /
Traceback (most recent call last):
  File "/usr/bin/emerge", line 3200, in ?
    mydepgraph.merge(mydepgraph.altlist())
  File "/usr/bin/emerge", line 1912, in merge
    retval=portage.doebuild(y,"merge",myroot,self.pkgsettings,edebug)
  File "/usr/lib/portage/pym/portage.py", line 2664, in doebuild
    if mydo!="manifest" and not fetch(fetchme, mysettings, listonly=listonly, fetchonly=fetchonly):
  File "/usr/lib/portage/pym/portage.py", line 1819, in fetch
    file_lock = portage_locks.lockfile(mysettings["DISTDIR"]+"/"+locks_in_subdir+"/"+myfile,wantnewlockfile=1)
  File "/usr/lib/portage/pym/portage_locks.py", line 93, in lockfile
    fcntl.lockf(myfd,fcntl.LOCK_EX|fcntl.LOCK_NB)
IOError: [Errno 13] Permission denied

alexander@blatt ~ $ emerge info | grep -i FEAT
FEATURES="autoconfig ccache distcc distlocks sandbox sfperms strict"

alexander@blatt ~ $ emerge info | grep DISTDIR
DISTDIR="/Gentoo/Portage/distfiles"

alexander@blatt ~ $ grep /Gentoo/Portage/distfiles /etc/autofs/auto.misc
distfiles       -fstype=nfs,bg,hard,tcp,rsize=8192,wsize=8192,nfsvers=3,timeo=14 server:/Gentoo/Portage/distfiles

Auf dem "server":

/Gentoo/Portage/distfiles                       *.bei.digitalprojects.com(sync,rw,no_root_squash)

Auf dem "server" erhalte ich auch (wie es scheint) keine
Fehlermeldung.

Ratlos,

Alexander Skwar
-- 
gentoo-user-de@gentoo.org mailing list



      reply	other threads:[~2005-09-01 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22  9:08 [gentoo-user-de] distfiles mit NFS exportieren - kann keine Locks erzeugen :( Alexander Skwar
2005-08-22 10:14 ` Sevo Stille
2005-08-22 11:28   ` Alexander Skwar
2005-08-22 12:21     ` [gentoo-user-de] " Arnold Krille
2005-09-01 13:37       ` Alexander Skwar [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=4317042C.2070609@mid.email-server.info \
    --to=listen@alexander.skwar.name \
    --cc=gentoo-user-de@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