09-18-2010
Thanks for the replies. Ok. So the requirement is, I need to write a shell script such that it builds the parameter list with which it was invoked including any input or/and output redirection files, if any. So let's say a.sh is invoked as "sh a.sh arg1 arg2 < inp.dat", it should be able to build this argument list and store it in an usable variable or write it to another file. The contents being simply the invocation line - "sh a.sh arg1 arg2 < inp.dat". If say its invoked as "sh a.sh arg1 arg2", (the simplest case), it should be able to write this invocation line ("sh a.sh arg1 arg2") into a file.
Lets assume that we always want the "output" in another file. So, if the script is invoked as "sh a.sh arg1 arg2 < inp.dat > out.log", let it produce a file result.txt with contents "sh a.sh arg1 arg2 < inp.dat > out.log".
Hope am clear this time. I can understand the requirement is kind of weird!
Thanks again.
---------- Post updated at 01:25 PM ---------- Previous update was at 01:20 PM ----------
Missed adding in the last post that my only challenge it is to "read" the input and output redirection file name within the script. Otherwise, its simply looping through the parameter list. Pardon my ignorance!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Can anyone please tell me what these lines do?
ls >& outfile
ls outfile 2>&1
Thanks. (1 Reply)
Discussion started by: trivektor
1 Replies
2. Programming
Can you help me ?
I want to write a program ,which can open a input file (input.txt) and run as child process ,then write to output file (output.txt).......
char inFile="input.txt";
char outFile="output.txt";
int main(int argc, char **argv)
{
pid_t pid=1;
int no=0; // no. of... (5 Replies)
Discussion started by: cupid1575
5 Replies
3. Shell Programming and Scripting
All,
I have a requirement to write a script where I check for Input redirection when the script was executed, based on which I handle my logic. Below is the example:
my.script
#! /bin/ksh
# Not sure how to frame the if condition below
if ; then
echo "Input Redirected from a file"
... (7 Replies)
Discussion started by: bharath.gct
7 Replies
4. Shell Programming and Scripting
I know this is a simple matter, but I'm new to this.
I have a shell script that calls a sed script from within it. I want the output of the shell script to be based on the input file I pass as an argument to the original script. In other words...
./script.sh file.txt
(script.sh calls sed... (2 Replies)
Discussion started by: estebandido
2 Replies
5. Shell Programming and Scripting
I have a directory where i have *.sas; *.pl;*.sh and *.c scripts
I need to find out what are the child scripts and input output files for each script:
say I have a shell script which calls a perl script and a sas script:
In my first line I want
I a) the parent script name;
b) the... (1 Reply)
Discussion started by: ramky79
1 Replies
6. Shell Programming and Scripting
How do I print output and read input on the same line in ksh?
echo Hello, what is your name? read name (1 Reply)
Discussion started by: robin_simple
1 Replies
7. Shell Programming and Scripting
Hi,
#!/bin/bash
while ;
do
rm -f /tmp/pipe
mkfifo /tmp/pipe
./yuv4mpeg_to_v4l2 < /tmp/pipe &
mplayer tom_and_jerry.mp4 -vf scale=480:360 -vo yuv4mpeg:file=/tmp/pipe
sleep 65;
done
When I run this - after mplayer finishes playing video it says - Exiting... (End of... (2 Replies)
Discussion started by: ashokvpp
2 Replies
8. Shell Programming and Scripting
Hi,
when I try to redirect input and the command is described as a string within an array redirection does not work. why?
#!/bin/bash
dir=("tail < ./hello.txt")
tail < ./hello.txt #works
${dir} #does not work (2 Replies)
Discussion started by: heinzel
2 Replies
9. Shell Programming and Scripting
I have files named with different prefixes. From each I want to extract the first line containing a specific string, and then print that line along with the prefix.
I've tried to do this with a while loop, but instead of printing the prefix I print the first line of the file twice.
Files:... (3 Replies)
Discussion started by: pathunkathunk
3 Replies
10. Shell Programming and Scripting
Hi All
Please Help
Read input write multply output with creteria
Exemple i have file
abc 111 444
abc 111 444
def 111 444
def111 444
bbb 111 444
bbb 111 444
i would need write 3 files pos 1-3 is the Criteria
output would be file1 contains abc file2 def file3 bbb
... (3 Replies)
Discussion started by: tonyk334
3 Replies
LEARN ABOUT LINUX
ddi_intr_add_handler
ddi_intr_add_handler(9F) ddi_intr_add_handler(9F)
NAME
ddi_intr_add_handler, ddi_intr_remove_handler - add or remove interrupt handler
SYNOPSIS
#include <sys/types.h>
#include <sys/conf.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
int ddi_intr_add_handler(ddi_intr_handle_t *h, ddi_intr_handler_t inthandler, void *arg1, void *arg2);
int ddi_intr_remove_handler(ddi_intr_handle_t h);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI).
ddi_intr_add_handler()
h Pointer to the DDI interrupt handle
inthandler Pointer to interrupt handler
arg1 First argument for the interrupt handler
arg2 Second, optional, argument for the interrupt handler
ddi_intr_remove_handler()
h DDI interrupt handle
The ddi_intr_add_handler() function adds an interrupt handler given by the inthandler argument to the system with the handler arguments
arg1 and arg2 for the previously allocated interrupt handle specified by the h pointer. The arguments arg1 and arg2 are passed as the first
and second arguments, respectively, to the interrupt handler inthandler. See <sys/ddi_intr.h> for the definition of the interrupt handler.
The routine inthandler with the arguments arg1 and arg2 is called upon receipt of the appropriate interrupt. The interrupt handler should
return DDI_INTR_CLAIMED if the interrupt is claimed and DDI_INTR_UNCLAIMED otherwise.
The ddi_intr_add_handler() function must be called after ddi_intr_alloc(), but before ddi_intr_enable() is called. The interrupt must be
enabled through ddi_intr_enable() or ddi_intr_block_enable() before it can be used.
The ddi_intr_remove_handler() function removes the handler association, added previously with ddi_intr_add_handler(), for the interrupt
identified by the interrupt handle h argument. Unloadable drivers should call this routine during their detach(9E) routine to remove the
interrupt handler from the system.
The ddi_intr_remove_handler() function is used to disassociate the handler after the interrupt is disabled to remove dup-ed interrupt han-
dles. See ddi_intr_dup_handler(9F) for dup-ed interrupt handles. If a handler is duplicated with the ddi_intr_dup_handler() function, all
added and duplicated instances of the handler must be removed with ddi_intr_remove_handler() in order for the handler to be completely
removed.
The ddi_intr_add_handler() and ddi_intr_remove_handler() functions return:
DDI_SUCCESS On success.
DDI_EINVAL On encountering invalid input parameters.
DDI_FAILURE On any implementation specific failure.
CONTEXT
The ddi_intr_add_handler() and ddi_intr_remove_handler() functions can be called from kernel non-interrupt context.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
attributes(5), attach(9E), detach(9E), ddi_intr_alloc(9F), ddi_intr_block_enable(9F), ddi_intr_disable(9F), ddi_intr_dup_handler(9F),
ddi_intr_enable(9F), ddi_intr_free(9F), ddi_intr_get_supported_types(9F), mutex(9F), mutex_init(9F), rw_init(9F), rwlock(9F)
Consumers of these interfaces should verify that the return value is not equal to DDI_SUCCESS. Incomplete checking for failure codes could
result in inconsistent behavior among platforms.
If a device driver that uses MSI and MSI-X interrupts resets the device, the device might reset its configuration space modifications. Such
a reset could cause a device driver to lose any MSI and MSI-X interrupt usage settings that have been applied.
The second argument, arg2, is optional. Device drivers are free to use the two arguments however they see fit. There is no officially rec-
ommended model or restrictions. For example, an interrupt handler may wish to use the first argument as the pointer to its softstate and
the second argument as the value of the MSI vector.
22 Apr 2005 ddi_intr_add_handler(9F)