From: Steve Dickson <SteveD@redhat.com>
To: Giulio Troccoli
<Giulio.Troccoli-xnMMdYoS6WpEKMMhf/gKZA@public.gmane.org>
Cc: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: [NFS] Compileing nfs-utils 1.1.5 on RHEL4 fails in tcpwrapper.c
Date: Tue, 31 Mar 2009 15:50:23 -0400 [thread overview]
Message-ID: <49D273FF.8060701@RedHat.com> (raw)
In-Reply-To: <6680A70380E6BA44A2D94ED7085718EE066A0807B0@ln1exc03>
Giulio Troccoli wrote:
>>> From time to time the build failes becuase some files are not
>>> available when they are compiled. This is not strictly
>> true, the file
>>> is available but the building machine is told it's not.
>> Make sure the time on all the machines are synced with
>> something like ntpd.
>
> Could you explain to me why the time is important? It might sound as a silly question, but as I see it it's just one portion of a file system in the remote machine mounted on the file system on the building machine.
>
>>> I don't know much about NFS and the option I chose for the
>> configure
>>> script are just becuase otherwise it didn't compile. So, do
>> you guys
>>> think that even without nfsv4, gss and tcp-wrapper I would
>> achive what I need?
>> Not clear... There is a very good change running such a new
>> nfs-utils on an legacy release might cause more problem...
>
> Sorry, now that I read it again I see it's not very clear.
>
> The files on the remote machine are only read by the building machine.
> Nothing is written on the NFS mounted file system by the building
> machine. NFS is used so that we can share source code among
> differente building machines. To achive this, do I need nfsv4, gss
> and tcp-wrapper?
No. You do not need those to achive what your are looking for.
> In other words, what are nfsv4, gss and tcp-wrapper?
nfsv4 - is the latest NFS protocol version
gss - used to secure NFS mounts
tcp-wrapper - is a mechanism to allow or deny hosts access to
your NFS server.
>
> Thanks for your help, it's very much appreciated.
np..
steved.
------------------------------------------------------------------------------
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
prev parent reply other threads:[~2009-03-31 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 16:37 [NFS] Compileing nfs-utils 1.1.5 on RHEL4 fails in tcpwrapper.c Giulio Troccoli
2009-03-27 13:59 ` Steve Dickson
[not found] ` <49CCDBD2.2000709-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-03-27 14:15 ` Giulio Troccoli
[not found] ` <49CD07F5.1070005@RedHat.com>
[not found] ` <49CD07F5.1070005-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-03-30 9:06 ` Giulio Troccoli
2009-03-31 19:50 ` Steve Dickson [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=49D273FF.8060701@RedHat.com \
--to=steved@redhat.com \
--cc=Giulio.Troccoli-xnMMdYoS6WpEKMMhf/gKZA@public.gmane.org \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.