02-28-2013
I believe your auto.master file should read
/nethome /etc/auto.nethome --timeout=300
not
/nethome /etc.auto.nethome --timeout=300
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
folks;
How can i give a group a sudo permission to execute only some command "like start/stop Apache", so every user in that group can sudo to use this as himself, i mean when he tries to sudo, he will be asked for a password (and make it so he must use his own NT password not a generic one) then... (6 Replies)
Discussion started by: Katkota
6 Replies
2. UNIX for Dummies Questions & Answers
Hello All,
I receive a file from another server with file permission rw-r--r-- and owner of the file is the sFTP login id and group is also different from my login id.
Due to this I cannot move the file from and also cannot do anything on it.
Can anyone help on how to change the file... (2 Replies)
Discussion started by: maddy911
2 Replies
3. UNIX for Dummies Questions & Answers
Folks;
I'm mounting a directory on a different SUSE 10 server from my SUSE server fine. using this mount command:
# mount 192.168.132.11:/var/local/new /var/local/new
this command above works fine but when i added a new line to my "/etc/fstab" to be mounted automatically every time i... (2 Replies)
Discussion started by: Katkota
2 Replies
4. Shell Programming and Scripting
hello
I m trying to enter in a folder through my script but getting permission denied error ..
Is there any command or somthing else so that i can access these folder through my script. (3 Replies)
Discussion started by: urfrnddpk
3 Replies
5. Red Hat
OK,
I'm running low on patience with how this is working out. I have a RHEL 5.4 64bit server running 389 directory services and NFS4. I set up the schema for automount, and I am having some issues.
I'm relatively new to both LDAP and Automount, and NFS4 has thrown me some curves vs NFS2/3.... (6 Replies)
Discussion started by: mark54g
6 Replies
6. OS X (Apple)
-rw-r--r-- 1 root wheel 1676 Jul 8 13:40 group
-rw-r--r-- 1 root wheel 3669 Feb 25 2010 passwd
-r--r----- 1 root wheel 1242 Jan 26 2010 sudoers
I can read group and passwd, but i cant read sudoers.. why?
I am curenttly a staff member. (1 Reply)
Discussion started by: linuxstuff101
1 Replies
7. HP-UX
Good day guys,
I am very new in UNIX and am trying to install an application which uses an application ID that requires administrative privileges (Full control). In most cases, we use SUDO to grant access to this ID however the customer insisted NOT to use SUDO and Root ID is not to be used to... (1 Reply)
Discussion started by: mcdsweet98
1 Replies
8. Linux
Hi Team,
I am trying to delete the clearcase view in linux box. But i cant get, because my hostname is not configure under the at net directory in root dir.
Please advice on this.
Thanks,
Mani (2 Replies)
Discussion started by: Mani_apr08
2 Replies
9. AIX
Hi Team,
I am using AIX 6.1 version. I have two log id IDs say (user1 and user2)
Both users primary group is same. ex (group1)
I have created directory called /logs/app using user1 and permissions are like below
/logs ------ drwxrwxr-x
/logs/app ----- drwxrwxrwx
But all the process... (3 Replies)
Discussion started by: balasubramani04
3 Replies
10. AIX
Hi there,
I have a strange problem, I have a NFS server running AIX 7.1 TL3 SP3, let's call it server A. I have another AIX 7.1 TL3 SP3 server, let's call it server B, that's automounting a filesystem from server A.
When server B is automounting the filesystem from server A, I can't see any... (3 Replies)
Discussion started by: ce9888
3 Replies
nfsd(8) System Manager's Manual nfsd(8)
NAME
nfsd - The remote NFS compatible server
SYNOPSIS
/usr/sbin/nfsd [-t num_tcpthreads] [-u num_udpthreads]
The following form of the nfsd command is not recommended and is supported only for backward compatibility:
/usr/sbin/nfsd [numthreads]
FLAGS
Specifies a number of TCP server threads (per RAD) to spawn. A value of 8 is recommended as a start. Specifies a number of UDP server
threads (per RAD) to spawn. A value of 8 is recommended as a start.
DESCRIPTION
The nfsd daemon runs on a server machine to service NFS requests from client machines. The daemon spawns a number of server threads that
process NFS requests from client machines. At least one server thread must be running for a machine to operate as a server.
There are two types of server threads: a server thread that processes NFS requests sent using TCP and a server thread that processes NFS
requests sent using UDP. This is necessary because the kernel paths for UDP and TCP NFS messages are different. The -t option specifies
the number of TCP threads to run and the -u option specifies the number of UDP threads to run.
On systems that support Cache Coherent NUMA, the number of threads is per Resource Affinity Domain (RAD). As you add RADs, the NFS server
will automatically scale by creating additional threads. NFS requests are processed by a particular RAD based on the file being accessed;
this confines cached information about a file to a single RAD for efficiency. See numa_intro(3) for more information on the NUMA architec-
ture.
If you use the SysMan Menu to configure NFS, it sets the default at 8 UDP and 8 TCP threads. However, a user can have any number of TCP
and UDP nfsd threads running up to a maximum of 128 threads. The optimal number of TCP server threads and UDP server threads depends on
many factors. See nfsiod(8) for more information.
The server threads are implemented as kernel threads; they are part of Process ID 0, not the nfsd process. The ps axml command displays
idle server threads under PID 0. Idle threads will be waiting on nfs_udp_wait or nfs_tcp_wait. Therefore, if 16 server threads are config-
ured, only one nfsd process is displayed in the output from the ps command, although 16 server threads are available to handle NFS
requests.
Files that are larger than 2 gigabytes are exported as 2 gigabyte files when accessed by NFS Version 2. NFS Version 2 is a 32-bit proto-
col, therefore, the size and offset fields are 32-bit quantities (on Alpha UFS they are 64-bit quantities). Use caution when accessing
files larger than 2 gigabytes from NFS clients.
EXAMPLES
In the following example, 16 threads are run (8 for TCP and 8 for UDP): nfsd -t 8 -u 8
FILES
Specifies the command path Specifies the file for logging startup errors (before the server threads are started). Specifies the file for
logging NFS errors (after the server threads are started).
RELATED INFORMATION
Commands: mount(8), mountd(8), nfsconfig(8), nfsstat(8), portmap(8)
System calls: nfssvc(2) delim off
nfsd(8)