From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Cc: Lista Linux-BProc <bproc-users@lists.sourceforge.net>
Subject: Reading libs fails through NFS
Date: Mon, 17 Nov 2003 01:45:39 +0100 [thread overview]
Message-ID: <20031117004539.GA2155@werewolf.able.es> (raw)
Hi all...
Anybody has any idea about why this fails:
fd = open("/lib/libnss_files.so.2", O_RDONLY);
res = read(fd,buf,512);
/lib is NFS mounted:
192.168.0.1:/lib on /lib type nfs (ro,noatime,nfsvers=3,nolock,addr=192.168.0.1)
and the read fails.
The original code does a getprotobyname("tcp") (netpipe), that fails when it
tries to read the same lib.
The node boots via PXE, with a version of libnss_files.so.2 on the /lib present
in the initrd, which is replaced by the mounted one.
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrake Linux release 10.0 (Cooker) for i586
Linux 2.4.23-rc1-jam2 (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-4mdk))
next reply other threads:[~2003-11-17 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 0:45 J.A. Magallon [this message]
2003-11-17 1:24 ` Reading libs fails through NFS Trond Myklebust
2003-11-23 0:57 ` [BProc] " J.A. Magallon
2003-11-17 1:29 ` Valdis.Kletnieks
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=20031117004539.GA2155@werewolf.able.es \
--to=jamagallon@able.es \
--cc=bproc-users@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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