On 07/08/13 22:24, Amadeus W.M. wrote:
> Thank you, that's life saver.
>
> Behind I am, but then so is system-config-nfs because that's what I used
> to configure nfs, including the ports.
I don't use that tool. If it lead you down the garden path, you probably
should write a bugzilla.
>
> Whi
On Mon, 08 Jul 2013 13:29:44 +0800, Ed Greshko wrote:
> On 07/08/13 13:09, Amadeus W.M. wrote:
>> I normally have an nfs server running on one of my machines. Now nfs
>> itself and the portmapper start on fixed ports, but the rpc services
>> start on random ports so they need to be assigned fixed
On 07/08/13 13:09, Amadeus W.M. wrote:
> I normally have an nfs server running on one of my machines. Now nfs
> itself and the portmapper start on fixed ports, but the rpc services
> start on random ports so they need to be assigned fixed ports in
> /etc/sysconfig/nfs like so:
>
> LOCKD_TCPPORT=
I normally have an nfs server running on one of my machines. Now nfs
itself and the portmapper start on fixed ports, but the rpc services
start on random ports so they need to be assigned fixed ports in
/etc/sysconfig/nfs like so:
LOCKD_TCPPORT=4000
STATD_PORT=4002
RQUOTAD_PORT=4003
LOCKD_UDPPO
Restating the problem:
On the server, running FC15 (192.168.1.14):
(1) My /etc/exports file looks like this:
/home/magnusg/Music 192.168.1.12,192.168.1.13(rw,insecure,sync,nohide)
(2) Using the system-config-nfs "General Options tab" I have "Allow
connections from port 1024 and higher" checked.
(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/22/2011 11:20 PM, Genes MailLists wrote:
> On 10/22/2011 08:43 PM, Gerhard Magnus wrote:
>>
>> I didn't get anything running sealert -b. The widget "SELinux
>> Alert Browser" showed no alerts. In /var/log/messages I get this
>> message repeated
On 23 October 2011 23:11, Gerhard Magnus wrote:
> I can ping (and ssh) the server from the client.
> When I restart nfs and nfslock on the server I get this in the
> server /var/log/messages:
> PuteF kernel: [25572.902466] NFSD: Using /var/lib/nfs/v4recovery as the
> NFSv4 state recovery directory
Gerhard Magnus wrote:
>
>> On 10/23/2011 07:24 AM, Gerhard Magnus wrote:
>>> I have a small home LAN. I am running FC15 on the server. As I still
>>> have not made a full peace with FC15 I'm still running FC13 on the
>>> client. Several years and FC versions ago, someone on the list told me
>>> abo
I can ping (and ssh) the server from the client.
When I restart nfs and nfslock on the server I get this in the
server /var/log/messages:
PuteF kernel: [25572.902466] NFSD: Using /var/lib/nfs/v4recovery as the
NFSv4 state recovery directory
PuteF kernel: [25572.902504] NFSD: starting 90-second grac
On Sat, 2011-10-22 at 20:58 -0400, Tom Horsley wrote:
> On Sat, 22 Oct 2011 16:42:26 -0700
> Gerhard Magnus wrote:
>
> > I get this error message:
> > mount.nfs: Connection timed out
>
> Try restarting the NFS server on the host system and
> then try mounting the filesystem on the client
> again.
On 10/22/2011 08:43 PM, Gerhard Magnus wrote:
>
> I didn't get anything running sealert -b. The widget "SELinux Alert
> Browser" showed no alerts. In /var/log/messages I get this message
> repeated at intervals:
> Oct 22 17:37:49 PuteB mount[1460]: mount to NFS server '192.168.1.14'
> failed: Conn
On 10/22/2011 04:42 PM, Gerhard Magnus wrote:
> Is this the right mount command?
> mount -t nfs 192.168.1.14:/home/magnusg/Music /home/magnusg/Music
>
If this partition is listed in /etc/fstab, you should be able to get
away with this:
mount /home/magnusg/Music
or, if you really want to avoid t
On Sat, 22 Oct 2011 16:42:26 -0700
Gerhard Magnus wrote:
> I get this error message:
> mount.nfs: Connection timed out
Try restarting the NFS server on the host system and
then try mounting the filesystem on the client
again. I get the impression that systemd somehow
manages to start servers befo
On 10/22/2011 08:07 PM, Gerhard Magnus wrote:
>>
>>
>> Is this the right mount command?
>> mount -t nfs
>> 192.168.1.14:/home/magnusg/Music /home/magnusg/Music
>>
>> I get this error message:
>> mount.nfs: Connection timed out
On Sun, 2011-10-23 at 05:19 +0530, Soham Chakraborty wrote:
> Yes, mount command seems fine to me. What does this command say
>
> mount -t nfs,_netdev
> 192.168.1.14:/home/magnusg/Music /home/magnusg/Music
magnusg@PuteB Sat Oct 22 17:03:07
[1004] ~ $ su -c "mount -t nfs,_netdev
192.168.1.14:/home
Yes, mount command seems fine to me. What does this command say
mount -t nfs,_netdev 192.168.1.14:/home/magnusg/Music /home/magnusg/Music
--Soham
On Sun, Oct 23, 2011 at 5:12 AM, Gerhard Magnus wrote:
>
> > On 10/23/2011 07:24 AM, Gerhard Magnus wrote:
> > > I have a small home LAN. I am runnin
> On 10/23/2011 07:24 AM, Gerhard Magnus wrote:
> > I have a small home LAN. I am running FC15 on the server. As I still
> > have not made a full peace with FC15 I'm still running FC13 on the
> > client. Several years and FC versions ago, someone on the list told me
> > about this procedure for se
On 10/23/2011 07:24 AM, Gerhard Magnus wrote:
> I have a small home LAN. I am running FC15 on the server. As I still
> have not made a full peace with FC15 I'm still running FC13 on the
> client. Several years and FC versions ago, someone on the list told me
> about this procedure for setting up NF
I have a small home LAN. I am running FC15 on the server. As I still
have not made a full peace with FC15 I'm still running FC13 on the
client. Several years and FC versions ago, someone on the list told me
about this procedure for setting up NFS, which has been working fine...
until now.
no, I haven't seen it and tested it many times.
On Wed, Mar 3, 2010 at 10:36 AM, bruce wrote:
> hey gary...
>
> just wondering. i'm assuming that an nfs_12 client doesn't hang?
>
>
>
> On Wed, Mar 3, 2010 at 10:28 AM, gary artim wrote:
>> Hi All --
>>
>>
>> wondering if anyone has had any proble
hey gary...
just wondering. i'm assuming that an nfs_12 client doesn't hang?
On Wed, Mar 3, 2010 at 10:28 AM, gary artim wrote:
> Hi All --
>
>
> wondering if anyone has had any problems with nfs between an
> fc12_nfs_server and fc11_nfs_client? I have a client that periodically
> hangs on doi
Hi All --
wondering if anyone has had any problems with nfs between an
fc12_nfs_server and fc11_nfs_client? I have a client that periodically
hangs on doing something like:
tree /mynfs
or
find /mynfs
Basically a full metadata listing of the nfs share. The nics look fine
and the routing looks
22 matches
Mail list logo