02-26-2005
As I watched that thread unfold, I was very impressed with your patience. I would have bailed out a long time ago. I'm also impressed with your knowledge.
Taking this thread to PM would violate the spirit of
rule number 10. We may need to amend rule 10 to make that more explicit now that we have PM enabled. On the other hand, if the thread degenerated into chit-chat, continuing the thread would violate rule 3. As long as it's technical, the thread is the way to go. And I trust your judgement to know the difference.
We have longer threads. And many threads seem targeted to the original poster. I don't see any harm in either quality in a thread.
So my opinion: great work!
9 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Neo, if I have an old thread that is a few months old, and a few pages back in the forum it was posted in, is it ok to 'bump' it back to the front? or, would you rather i deleted the old thread, and just create a new one? btw the thread has no replies. (2 Replies)
Discussion started by: norsk hedensk
2 Replies
2. UNIX for Dummies Questions & Answers
i am tring to sort lots of data thats in many columns by just one column but, if I use sort +16 inputfile the column fluctuates because some of the rows have spaces etc within the text, so the end result is just a mess as it jumps around the columns depending whether it has spaces or not ....ie... (2 Replies)
Discussion started by: Gerry405
2 Replies
3. Solaris
Hi all!
1)Is there a way to write a program that will work on both solaris and intel based machines.
2)How can I achive this for a program that creates and synchronizes three threads.
Thank you.
vij. (3 Replies)
Discussion started by: vijlak
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
I have a program that has two types of threads:
1) Reader threads
2) Worker Threads
Readers: Their only job is to read files. They just read data from the files and put them into a buffer. They are obviously I/O intensive.
Workers: These are CPU intensive. They do some computation... (5 Replies)
Discussion started by: the_learner
5 Replies
5. UNIX for Advanced & Expert Users
Hi all,
How can I get the list of all Threads and the Total count of threads under a particular process ?
Do suggest !!
Awaiting for the replies !!
Thanks
Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies
6. Programming
Hello! I started studying studying about POSIX Threads a few days ago... so I am a little confused and I would appreciate some help!
I isolated this code... and I wonder if I could use threads in it!
#include <unistd.h>
#endif
#include <math.h>
//#include "main.h"
#include <sys/time.h>... (1 Reply)
Discussion started by: smurf2
1 Replies
7. Programming
Hello C programming fellows!!!
I'm doing a program with multiple threads in gnu/linux, ubuntu for beeing precise...
This program consist in multiple threads, as logical each thread do different things and communicate to each other using IPC.
The problem is that in "process 1" I have a... (1 Reply)
Discussion started by: Sandia_man
1 Replies
8. Post Here to Contact Site Administrators and Moderators
Dear admins,
it seems that some threads or even users have recently (~ 2 days or so) disappeared. Examples: giuliangiuseppe and greycells. The latter asked me for the solution I provided earlier this week.
What happened? Can you help?
Regards
Rüdiger (10 Replies)
Discussion started by: RudiC
10 Replies
9. Post Here to Contact Site Administrators and Moderators
Hello Admin,
The issue that i posted in the following threads has been resolved,
https://www.unix.com/ubuntu/266128-how-access-website-without-port-ubuntu-14-04-a.html
https://www.unix.com/red-hat/265635-error-while-extending-logicalvolume.html
Kindly close the threads.Thanks:) (1 Reply)
Discussion started by: gull05
1 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)