Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Reading runtime arguments from a file Post 81366 by reborg on Thursday 18th of August 2005 06:09:36 PM
Old 08-18-2005
Redirect stdin
Code:
command < responsefile

or a here document:
Code:
command <<EOF
y
n
n
y
n
y
EOF

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bash: Reading 2 arguments from a command line

If no arguments are entered I wanna be able to read 2 arguments, i have done like this but it doesnt work: x=0 until #loop starts do if ; then echo No arguments were entered, please enter 2 arguments. read $1 $2 elif || ; then echo $#... (0 Replies)
Discussion started by: Vozx
0 Replies

2. Shell Programming and Scripting

passing runtime arguments to a shell script...

hi I am new to shell programming.....my question is while running one of my shell program it stops in between to accept input from the user and proceeds furthur after giving input....I want to know whether I can set this input through some files so that the shell acript reads the input from the... (10 Replies)
Discussion started by: santy
10 Replies

3. UNIX for Advanced & Expert Users

connect problem for sctp socket (ipv6 socket) - Runtime fail Invalid Arguments

Hi, I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime. To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies

4. Shell Programming and Scripting

reading in arguments with spaces

I want to be able to read in input which contain spaces and put that into an array. Each field should be delimeted by a space and should be a different array element. However I cant get it to work. any tips? read input //type field1 field2 field3 echo "$input" array="$input" Thanks in... (11 Replies)
Discussion started by: Calypso
11 Replies

5. Shell Programming and Scripting

How to give runtime arguments to different program

I have a shell script that is attempting to call a c program. I call the c program with ./dictool dictool accepts arguments at runtime. It works by prompting the user for various commands, acting on those commands, spitting out an output, and then prompting for more commands. My question is,... (1 Reply)
Discussion started by: aarongoldfein
1 Replies

6. Shell Programming and Scripting

Passing arguments at runtime

Hi .. Can any one please tell how to pass argument to shell script at runtime? I want to implement funcnality just like bc, where we can provide input while script is running and can be used later in the same script. Thanks in advance... (1 Reply)
Discussion started by: kunjalhg
1 Replies

7. Shell Programming and Scripting

Reading arguments but exclusing some

I have a tcsh script which I pass arguments to. I want to store all the arguments except for the options. Currently I am using the line below, however I want to also exclude and variation of them (e.g. whether any letter is uppercase or lower case) Is there a neat way to do it? set... (0 Replies)
Discussion started by: kristinu
0 Replies

8. Shell Programming and Scripting

Reading arguments for a shell script from file

I have a shell script that takes 2 arguments. I will have to execute this script multiple times with different values for the arguments. for example, ./shscript env1 value1 ./shscript env1 value2 ./shscript env2 value3 ./shscript env3 value4 ./shscript env1 value5 ./shscript env3... (24 Replies)
Discussion started by: goddevil
24 Replies

9. Shell Programming and Scripting

Multiple runtime arguments

I am passing 3 runtime arguments to a shell script $path crtl1 crtl2 the crtl files contains data(filename|date|count) filename.txt|02/05/2010|10 The path contains the original data file,the code should fetch (filename|date|count) from original data file and it should match... (7 Replies)
Discussion started by: Prashanth B
7 Replies

10. Programming

Reading structured arguments

I am passing an argument to a C++ program which is going to look like I need to get the integers into arrays a, b, c, d with a= 12,12,34,2,12 b= 34,4,2,1,23 c= 5,5,4,4,13 d= 6,6,6,6,5 (5 Replies)
Discussion started by: kristinu
5 Replies
PS(1)							      General Commands Manual							     PS(1)

NAME
ps - process status SYNOPSIS
ps [ acgklnrtuwxU# [ core [ swap [ system ] ] ] ] DESCRIPTION
Ps prints certain indicia about active processes. To get a complete printout on the console or lpr, use ``ps axlw'' For a quick snapshot of system activity, ``ps au'' is recommended. A hyphen may precede options with no effect. The following options may be specified. a asks for information about all processes with terminals (ordinarily only one's own processes are displayed). c causes only the comm field to be displayed instead of the arguments. (The comm field is the tail of the path name of the file the process last exec'ed.) This option speeds up ps somewhat and reduces the amount of output. It is also more reliable since the process can't scribble on top of it. g asks for all processes. Without this option, ps only prints ``interesting'' processes. Processes are deemed to be uninteresting if they are process group leaders, or if their arguments begin with a `-'. This normally eliminates shells and getty processes. k causes the file /usr/sys/core is used in place of /dev/kmem and /dev/mem. This is used for postmortem system debugging. l asks for a long listing. The short listing contains the user name, process ID, tty, the cumulative execution time of the process and an approximation to the command line. n asks for numeric rather than symbolic wchans. This flag implies the ``l'' flag. r asks for ``raw'' output. A non-human readable sequence of structures is output on the standard output. There is one structure for each process, the format is defined by <psout.h> tttyname restricts output to processes whose controlling tty is the specified ttyname (which should be specified as printed by ps, including t? for processes with no tty). This option must be the last one given. u A user oriented output is produced. This includes the name of the owner of the process, process id, nice value, size, tty, cpu time used, and the command. w tells ps you are on a wide terminal (132 columns). Ps normally assumes you are on an 80 column terminal. This information is used to decide how much of long commands to print. The w option may be repeated, e.g. ww, and the entire command, up to 128 characters, will be printed without regard to terminal width. x asks even about processes with no terminal. U causes ps to update a private database where is keeps system information. Thus ``ps -U'' should be included in the /etc/rc file. # A process number may be given, (indicated here by #), in which case the output is restricted to that process. This option must also be last. A second argument tells ps where to look for core if the k option is given, instead of /usr/sys/core. A third argument is the name of a swap file to use instead of the default /dev/swap. If a fourth argument is given, it is taken to be the file containing the system's namelist. Otherwise, ``/unix'' is used. The output is sorted by tty, then by process ID. The long listing is columnar and contains F Flags associated with the process. These are defined by #define lines in /usr/include/sys/proc.h. S The state of the process. 0: nonexistent; S: sleeping; W: waiting; R: running; I: intermediate; Z: terminated; T: stopped. UID The user id of the process owner. PID The process ID of the process; as in certain cults it is possible to kill a process if you know its true name. PPID The process ID of the parent process. CPU Processor utilization for scheduling. PRI The priority of the process; high numbers mean low priority. NICE Used in priority computation. ADDR The memory address of the process if resident, otherwise the disk address. SZ The size in blocks (512 bytes) of the memory image of the process. WCHAN The event for which the process is waiting or sleeping; if blank, the process is running. TTY The controlling tty for the process. TIME The cumulative execution time for the process. COMMAND The command and its arguments. A process that has exited and has a parent, but has not yet been waited for by the parent is marked <defunct>. Ps makes an educated guess as to the file name and arguments given when the process was created by examining memory or the swap area. The method is inherently some- what unreliable and in any event a process is entitled to destroy this information, so the names cannot be counted on too much. FILES
/unix system namelist /dev/kmem kernel memory /dev/swap swap device /usr/sys/core core file /dev searched to find swap device and tty names /var/run/psdatabase system namelist and device information SEE ALSO
kill(1), w(1), pstat(8) BUGS
Things can change while ps is running; the picture it gives is only a close approximation to reality. Some processes, typically those in the background, are printed with null or garbaged arguments, even though the process has not swapped. (Sometimes ps even loses on its own arguments!) In these cases, the name of the command is printed in parentheses. When automatic crash dumps are enabled, /usr/sys/core is not a sensible default core file name. 3rd Berkeley Distribution PS(1)
All times are GMT -4. The time now is 06:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy