search for: myarg1

I'm starting to write an AGI script. I want to pass more than one parameter to the script, but seem to be unable to. extensions.conf: exten => 85,1,AGI(/etc/asterisk/agi/args.agi,myarg1,myarg2) args.agi: #!/usr/bin/perl print STDERR "FNORD prog = $0\n"; print STDERR "FNORD arg 1 = $ARGV[0]\n"; print STDERR "FNORD arg 2 = $ARGV[1]\n"; print STDERR "FNORD arg 3 = $ARGV[2]\n"; print STDERR "FNORD arg 4 = $ARGV[3]\n"...

I would like to instrument certain function calls with a function call of my own that takes some of the same arguments. For example, I would like to instrument calls to free with some function foo, so the C code would look like: foo(myarg1, myarg2, ptr); free(ptr); The problem occurs when I grab the arg from the free function and try to pass it to foo... if (isCallToFree(&I)) { Value* P; if (Function *F = I.getCalledFunction()) { Function::arg_iterator ait = F->arg_begin(); if (ait) { P = &(...

...sed on who takes the call i do: exten => s,1,answer() exten => s,1,Queue(myQueue,,,,,,myMacro) but, there is no arguments there, right? what about use exten => s,1,answer() exten => s,1,Queue(myQueue,,,,,,myMacro,arg1) (remember that macro works like exten => s,n,Macro(myMacro,myArg1,myArg2), that means, concatenate args after macro name, separate with comas. but.... Queue takes that thing after comas like other arguments OF QUEUE, not subargs of args. this is, my second example says, Queue(myQueue,,,,,,myMacro,arg1), but "arg1" is taken like queue argument means Go...

...a mention in the commit message as intentional. I'm also seeing a common pattern of assigning pid=$(cat file.pid) right after calling start_nbdkt. Would it be worth changing the signature of start_nbdkit() to also populate a pid variable on success, as in: start_nbdkit blocksize1.pid pid1 myarg1 start_nbdkit() { pidfile=$1 pidvar=$2 shift 2 ... pid=$(cat $pidfile) eval $pidvar=$pid which would also have the added benefit of avoiding the regression of pid1 not being set if the second nbdkit process doesn't start? But overall, I like the idea of refactoring the comm...

Hi Community, I have a question about how to pass command line parameters to R script running in the batch mode. The problem is: there is a banch of data files which are to be processed by R script called from a web-server, i.e. in the batch mode. The web server generates data files and passes their names calling 'R CMD BATCH' one by one for every file. Now the question is how to

Scott Ricketts wrote: > I would like to instrument certain function calls with a function call > of my own that takes some of the same arguments. For example, I would > like to instrument calls to free with some function foo, so the C code > would look like: > > foo(myarg1, myarg2, ptr); > free(ptr); > > The problem occurs when I grab the arg from the free function and try > to pass it to foo... > > if (isCallToFree(&I)) { > Value* P; > if (Function *F = I.getCalledFunction()) { > Function::arg_iterator ait = F->arg...

...or increase in time. > I'm also seeing a common pattern of assigning pid=$(cat file.pid) > right after calling start_nbdkt. Would it be worth changing the > signature of start_nbdkit() to also populate a pid variable on > success, as in: > > start_nbdkit blocksize1.pid pid1 myarg1 > > start_nbdkit() > { > pidfile=$1 > pidvar=$2 > shift 2 > ... > pid=$(cat $pidfile) > eval $pidvar=$pid It was nice that start_nbdkit has the same "signature" as a regular nbdkit command. > which would also have the added benefit of avoiding...

Combine much common code into tests/functions.sh. Patch 1: Preparation for patch 3. Patch 2: Fix a long-standing bug in how man pages links are generated. Patch 3: Common code for iterating a test function over every plugin. Patch 4: Common code for starting nbdkit in a test and waiting for the PID file to appear. This is the largest and most complex of the patches but is