read function Post: 19419

10 More Discussions You Might Find Interesting

1. Programming

read a file wich fscanf() in a function

I use fopen, fscanf, fclose to read a file. It can work well. since many files should be read, a function is created with the same code. But in the function, fscanf can not work well. for example, the first line of the the file is: > filename but the fscanf will give: 207/23/eee/34 it appears...

2. Programming

Cannot read a file with read(fd, buffer, buffersize) function

# include <stdio.h> # include <fcntl.h> # include <stdlib.h> # include <sys/stat.h> int main(int argc, char *argv) { int fRead, fPadded, padVal; int btRead; int BUFFSIZE = 512; char buff; if (argc != 4) { printf ("Please provide all of the...

3. Shell Programming and Scripting

read statement not working in a function

Pls this is emergency.I have written a script which is taking input from another script. and the contents of my second script are acting as functions to my main script.Now the problem is that in one of the functions i want the script ececution to stop and start when user enters any character r...

4. UNIX for Dummies Questions & Answers

Can we read in variable into function in Unix?

can u read variables into function in unix like java or c++ eg sum($1) { if echo "$1 is equal to yes" else echo "$1 not equal to yes" } and if so what r the rulz to using function in unix for using functions thanks in advance :confused:

5. UNIX for Dummies Questions & Answers

Can you read in variable into function in Unix?

can you read variables into function in unix like java or c++ eg sum($1) { if echo "$1 is equal to yes" else echo "$1 not equal to yes" } and if so what are the rules to reading variables into function in unix thanks in advance for your answer

6. Shell Programming and Scripting

Help with grep and read function in a BASH Script

I'm putting together a script that will search my mail archives for emails that meet certain criteria and output the files to a text file. I can manually cat that text file and pipe it into sendmail and it will work (i.e. cat /pathtofile/foo.txt | sendmail -t me@company.com) My script sends...

7. Shell Programming and Scripting

bash read within function with arguments

I have trouble getting this logic to work #!/bin/bash function assign_var(){ while do read -p "$2 :" $3 done } assign_var '$IPADDRESS' ipaddress IPADDRESS Basicly, i want to make sure that entry is made (i can add more sophisticated checks later), but the idea is to recycle...

8. UNIX Desktop Questions & Answers

AIX how to read the file in function again and again

dear friends I have a wrote a shell script which works like this. 1.) a command is executed and the log is moved in the file. 2.) this file is copied in to the other file. 3.) used a grep command to find a particular word. 4.) if a particular word is there then the script will go to next...

9. Shell Programming and Scripting

[Bash] Read History function & Read Arrowkeys

Hi. How can I create a history function? (By "read" command or so) & How can I configure a read command so that the arrow keys are not displayed so funny? (^[[A) Thanks in advance.

10. Shell Programming and Scripting

While read won't run keyboard function

I am using while read do/ done to retrieve menu item. Works as advertised, no problem. I am using this hack function "pause" to stop script execution and wait for keyboard "enter" key to continue. Sort of break point function. Also works fine with one exception - it does not work when used...

LEARN ABOUT OSF1

biod

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)