07-24-2014
This is a Linux machine, to be clear. But I guess autmount still has the same function, at least for the --timeout part.
So, If I updated automount's timeout value with a timeout value of 10 mins and reload autofs service, would it automatically unmount the idle clients after 10 minutes?
9 More Discussions You Might Find Interesting
1. Solaris
Ladies and Gentlemen:
I have successfully configured a Solaris 8 server with Jumpstart! I can Jumpstart Solaris 8 client systems with no problem. My configuration is as follows:
Jumpstart Server: Solaris 8 patched with Recommended Patches from June 05.
I have installed Solaris 8 in... (4 Replies)
Discussion started by: rambo15
4 Replies
2. AIX
I work for a fairly large organization who recently tasked me with securing our telnet services with IPsec. We have a large mixed environment where most of our servers are running unsecured telnet. ssh was my first suggestion but because of the cost of purchasing an enterprise license for a fips... (2 Replies)
Discussion started by: dgaixsysadm
2 Replies
3. Solaris
Hello,
I have a centos as nfs server, its name is centos_A.
After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/*
But,
My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies
4. AIX
I have an NFS file system mounted on one of my AIX servers with "mount -v cifs".. The server from which the file system was mounted has crashed and now my "df -g" output is hanging. Is there any was to unmount this NFS file system? I have tried "umount -f". Doesn't work.
Or is there any way in... (6 Replies)
Discussion started by: wibhore
6 Replies
5. UNIX for Advanced & Expert Users
Hello;
I work now with a team which has based her "applications" on the following schema:
1 NFS client C1 (linux redhat 5) writes a file fic.dat on a NFS SERVER S (RH 5)
Another NFS client C2 is waiting for the same file fic.dat (on NFS server S1), and, when "fic.dat" appears, then makes... (8 Replies)
Discussion started by: SolarMax
8 Replies
6. IP Networking
All of sudden in this morning, some computers could not connect to our UNIX server while other still could.
Some computers could ping the server while some could not.
Same on the server side.
It could ping some clients but not some.
All Windows clients could ping each other.
And more, the... (1 Reply)
Discussion started by: jonapa
1 Replies
7. Programming
Hello,
I have a question: I want to create a n client to one server connection. This is the client-server algorithm.
Enybody help to make the changes? (0 Replies)
Discussion started by: MaHmur
0 Replies
8. Solaris
Hi,
I am having some NFS directory consistency problems with the below setup on a local (192.) network:
1. Different permissions (chmod) for the same NFS dir are reflected on different clients.
2. (more serious) an NFS dir created on client1 cannot be accessed on client2; this applies to some... (10 Replies)
Discussion started by: cosmojetz
10 Replies
9. AIX
Hi 2 ALL,
try to run NFS Server in AIX 7.1 :
1. Step by step on NFS Server node
mkdir /tmp/test
chgrp staff /tmp/test
chmod 775 /tmp/test-- create export directory (fs)
mknfsexp -d /tmp/test -t ro
exportfs -va
show mount -e
:/# exportfs -av
exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies
NFSD(8) BSD System Manager's Manual NFSD(8)
NAME
nfsd -- remote NFS server
SYNOPSIS
nfsd [-6rut] [-n num_threads]
DESCRIPTION
nfsd runs on a server machine to service NFS requests from client machines. At least one nfsd must be running for a machine to operate as a
server.
Unless otherwise specified, four servers for UDP transport are started.
The following options are available:
-r Register the NFS service with rpcbind(8) without creating any servers. This option can be used along with the -u or -t options to
re-register NFS if the portmap server is restarted.
-n Specifies how many server threads to create. The default is 4. A server should run enough threads to handle the maximum level of
concurrency from its clients.
-6 Listen to IPv6 requests as well as IPv4 requests. If IPv6 support is not available, nfsd will silently continue and just use IPv4.
-t Serve TCP NFS clients.
-u Serve UDP NFS clients.
For example, ``nfsd -t -u -n 6'' serves UDP and TCP transports using six threads.
nfsd listens for service requests at the port indicated in the NFS server specification; see Network File System Protocol Specification, RFC
1094 and NFS: Network File System Version 3 Protocol Specification.
The nfsd utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
nfsstat(1), nfssvc(2), mountd(8), rpcbind(8)
HISTORY
The nfsd utility first appeared in 4.4BSD.
BSD
March 17, 2008 BSD