07-24-2001
I think the chances are pretty good.! I will start a new section called something like "FAQ: The Best Posts of UNIX.COM" and with subsections appropriately made. We will copy some of the best posts on many subjects to that section and lock the threads, as a FAQ. Structure TBD.
This will help keep the server faster so people don't have to search too much .... and try to think of clever key words (which can be helpful if English is not your native language.)
Great suggestion
![Smilie Smilie](https://www.unix.com/images/smilies/smile.gif)
Thanks.
Please be patient and I'll start this when I have some time. Suggestions on threads to include welcome, of course!! If you have any particular threads you like that cover FAQ questions, please post them here.
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Just like we have a section "Unix for dummies..." , why not have a section on UNIX BACKUP AND RECOVERY
Thanks
:) (3 Replies)
Discussion started by: kapilv
3 Replies
2. Post Here to Contact Site Administrators and Moderators
Since when did unix.com become unixandwindows.com? Just my opinion, but I think this forum should stick to what it does well: providing Unix knowledge. Is there any user preference for ignoring a particular topic section? (4 Replies)
Discussion started by: PxT
4 Replies
3. UNIX for Dummies Questions & Answers
what is a critical section?why multipleprocesses or multiplethreads cant be given a chance to access the critical section?
please explain me with an example.
thanks (3 Replies)
Discussion started by: compbug
3 Replies
4. OS X (Apple)
Why I can see 3 from 80 topics in apple section? (1 Reply)
Discussion started by: kezzol
1 Replies
5. Post Here to Contact Site Administrators and Moderators
Hi
Just a thought if it already hasn't been suggested.
While looking at the forums I thought it might be a good idea under somewhere like 'special forums' add a section called 'projects'. I think this would be good for people to be able to post projects they have created.
For example I am... (3 Replies)
Discussion started by: woofie
3 Replies
6. Shell Programming and Scripting
I have a list of Servers in no particular order as follows:
virtualMachines="IIBSBS IIBVICDMS01 IIBVICMA01"And I am generating some output from a pre-existing script that gives me the following (this is a sample output selection).
9/17/2010 8:00:05 PM: Normal backup using VDRBACKUPS... (2 Replies)
Discussion started by: jelloir
2 Replies
7. Shell Programming and Scripting
Hey,
I have a problem about how to get one section of a file?
I'm new to shell, but by reading some tutorial, I think I can use awk to do this.
my input file:
>ref|ZP_04937576.1|
ECRINAEDPKTFMPSPGKVKHFHAPGGNGVRVDSHLYSGYSVPPNYDSLVGKVITYGAD
DEALARMRNALDELIVDGIKTNTELHKDLVRDAAFCKGGVNIHYLE... (11 Replies)
Discussion started by: ritacc
11 Replies
8. Shell Programming and Scripting
I need to remove the <BR> from all sections of a page, except what is between a section of text:
#!/bin/sh
sed '
/Testing Considerations/,/<B>PT# - Description:/ ! {
s/<BR>//
}
'
But this isn't working. I'm not using the ! operator correctly, can someone... (2 Replies)
Discussion started by: dba_frog
2 Replies
9. Shell Programming and Scripting
I have searched in a variety of ways in a variety of places but have come up empty.
I would like to prepend a portion of a section header to each following line until the next section header. I have been using sed for most things up until now but I'd go for a solution in just about anything--... (7 Replies)
Discussion started by: pagrus
7 Replies
10. Shell Programming and Scripting
I have a script that outputs this as a file
John Smith
----------------
memberOf: example1;sampletest;test
memberOf: example2;sampletest;test
memberOf: example3;sampletest;test
memberOf: example4;sampletest;test
A Member of 4 Groups
Sally Smith
----------------
memberOf:... (4 Replies)
Discussion started by: ajetangay
4 Replies
nfsiod(8) System Manager's Manual nfsiod(8)
NAME
nfsiod, biod - The local NFS compatible asynchronous I/O daemon
SYNOPSIS
nfsiod [ numthreads ]
DESCRIPTION
The nfsiod daemon runs on an NFS compatible client machine and spawns several IO threads to service asynchronous I/O requests to its
server. The I/O threads improve performance of both NFS reads and writes. Both try to enlist the aid of an idle I/O thread. If none is
available, the process itself issues the request to the server and waits for the reply.
The optimum number of I/O threads to run depends on many variables, such as how quickly the client will be writing, how many files will be
accessed simultaneously, and the behaviour of the NFS server. For use with a Tru64 UNIX server, 7 is a good number of I/O threads for most
systems.
When reading, if the client believes the process is reading a file sequentially, it requests an I/O thread to read a block ahead of what
the process is currently requesting. If the readahead completes before the process asks for that block, then the subsequent read system
call for that data completes immediately and does not have to wait for the NFS request to complete. Read ahead will be triggered again so
the read may find that next block available as well.
When writing a file, the client takes the process's data, passes the request to an I/O thread and immediately returns to the process. If
the process is writing data faster than the network or server can process, then eventually all the I/O threads become busy and the process
has to handle a NFS write itself. This means the process has to wait until the server finishes the write. For Tru64 UNIX servers, the NFS
block size is 8Kb and UFS tries to cluster I/O 64Kbs at a time. If the client is running with 7 I/O threads, 8 write requests can be in
progress at once. This allows the client and server to write data 64Kbs at a time and is the reason for recommending 7 I/O threads.
Unlike nfsd, each client thread can use either UDP or TCP. However, if TCP mounts are active, the nfsiod process will time out, close idle
TCP connections, and acknowledge any connections closed by the server.
The nfsiod process is also responsible for syncing the access time and modify times for special files and named pipes (fifos). Because I/O
to these files does not go through the NFS server, NFS clients have to directly update the access time and modify time attributes.
The client threads are implemented as kernel threads; they are part of Process ID 0, not the nfsiod process. The ps axml command displays
idle I/O threads under PID 0. Idle threads will be waiting on nfsiod_wait. Therefore, if 7 I/O threads are configured, only 1 nfsiod
process is displayed in the output from the ps command, although 7 client threads are available to handle NFS requests.
FILES
Specifies the command path Specifies the file for logging NFS activity.
RELATED INFORMATION
Commands: nfsd(8), nfsstat(8)
Daemons: async_daemon(2) delim off
nfsiod(8)