Sponsored Content
Full Discussion: Safely parsing parameters
Top Forums Shell Programming and Scripting Safely parsing parameters Post 302590155 by methyl on Saturday 14th of January 2012 11:18:34 AM
Old 01-14-2012
Quote:
I have a string like

Code:
root=/dev/sda3 noacpi foo "Baz mumble"
Sorry to be a pedant, or just plain thick! My question in post #10 still applies, but I'll rephrase it.
How did we arrive at the situation in post #1. i.e. What code, parameters or whatever produced or defined "root". I can achieve the assignment with backslashes but I just wondered whether is a free-standing command, a line from an parameter file or just (as I now suspect) a visual representation of what is in the environment variable without any syntax intended.

I have had a similar problem when writing a script to search thousands of alien scripts written to no particular standard. It was important that the search process never executed arbitary code.

Last edited by methyl; 01-14-2012 at 12:24 PM..
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Parsing Parameters

How do you pass parameters over to another script and run the receiving script? . Here is an example of what I am talking about. for x in `cat Allx` do su myaccount -c "/temp/scripts/temp_script $x" > /dev/null 2>$1 $ done I was expecting the tem_script to be... (1 Reply)
Discussion started by: odogbolu98
1 Replies

2. Shell Programming and Scripting

Help with parsing parameters

Hi:- I need to parse a script 3 parameters (file, subject and email address). This is what I currently have: allargs=$* argcount=`echo $allargs | awk -F: '{ print NF }' ` # Total Number of arguments pdffile=`echo $allargs | awk -F: '{ print $1 }' ` # PDF/binary file to be encoded... (4 Replies)
Discussion started by: janet
4 Replies

3. UNIX for Advanced & Expert Users

Can I safely kill vdump?

Sceduled backups with vdump have been delayed as a mounted system had crashed while I was away for 2 weeks. Now there are 5 simultaneous vdumps running very slowly. The full system backup usually takes a whole weekend. Can I safely kill these? (I will have to live without a backup untill next... (4 Replies)
Discussion started by: nickt
4 Replies

4. Shell Programming and Scripting

Help parsing job script input parameters

I have a job script that runs with input parms from the command line. job.sh -p parm1_parm2_parm3_parm4_file_1.dat The parms are separated by _ The last parm is a file name and can have an _ in the name. I currently use the following commands to extract the parms parm1=`eval echo... (3 Replies)
Discussion started by: jclanc8
3 Replies

5. Shell Programming and Scripting

How to safely rm/mv files/directory

Hi all, Am writing a script that does a rm/mv if a file exist, however, in one scenario, one of the variables which is supposed to a variable for a directory is undefined/blank so instead of the variable resolving to /tmp/logfile.dmp, it resolves instead to / so the rm translates to a rm /... (2 Replies)
Discussion started by: newbie_01
2 Replies

6. Programming

Value changed when parsing parameters

I get a strange problem here, and ask for help. (gdb) 28 set_file_bit( file, bytePos, bitPos, argv ); (gdb) p argv $3 = 0xbfffef5c "00" (gdb) s set_file_bit (file=0x804b008, bytePos=2, bitPos=2, binary=0x80490e5 "11") at util/file.c:112 ... (2 Replies)
Discussion started by: 915086731
2 Replies

7. Solaris

How to remove soft link safely

Greetings, I need some help performing a system admin function that I have been tasked with. The request seems simple enough, but my feeling is that it might be more complicated than it seems. Here is what i've been tasked with: SunOS 5.10 Generic_142900-15 sun4u sparc SUNW,SPARC-Enterprise... (3 Replies)
Discussion started by: Harleyrci
3 Replies

8. Solaris

need to safely reboot to cdrom

I am using: reboot -- cdrom However I'm afraid of causing file system errors/corruption. I've seen many threads say that init 6 is safer, but I need to get to CDROM. Is there a command that is as safe as init, but can boot to cdrom, or should I not worry so much about the reboot... (5 Replies)
Discussion started by: lcoreyl
5 Replies

9. Red Hat

Can all files under /tmp be safely removed

I wanted to know whether all files under /tmp can be safely removed. I guess that /tmp may also have temporary files for applications currently being worked on, so at the most those applications may just shut down. I hope that my question is clear whether all files under /tmp can be safely... (5 Replies)
Discussion started by: RHCE
5 Replies
ePerl(3pm)						User Contributed Perl Documentation						ePerl(3pm)

NAME
Parse::ePerl - Perl interface to the ePerl parser SYNOPSIS
use Parse::ePerl; $rc = Parse::ePerl::Preprocess($p); $rc = Parse::ePerl::Translate($p); $rc = Parse::ePerl::Precompile($p); $rc = Parse::ePerl::Evaluate($p); $rc = Parse::ePerl::Expand($p); DESCRIPTION
Parse::ePerl is the Perl 5 interface package to the functionality of the ePerl parser (see eperl(1) for more details about the stand-alone program). It directly uses the parser code from ePerl to translate a bristled script into a plain Perl script and additionally provides functions to precompile such scripts into P-code and evaluate those scripts to a buffer. All functions are parameterized via a hash reference $p which provide the necessary parameters. The result is a return code $rc which indicates success(1) or failure(0). PREPROCESSOR: $rc = Parse::ePerl::Preprocess($p) This is the ePerl preprocessor which expands "#include" directives. See eperl(1) for more details. Possible parameters for $p: Script Scalar holding the input script in source format. Result Reference to scalar receiving the resulting script in bristled Perl format. BeginDelimiter Scalar specifying the begin delimiter. Default is ``"<:"''. EndDelimiter Scalar specifying the end delimiter. Default is ``":>"''. INC A reference to a list specifying include directories. Default is "@INC". TRANSLATION: $rc = Parse::ePerl::Translate($p) This is the actual ePerl parser, i.e. this function converts a bristled ePerl-style script (provided in "$p-"{Script}> as a scalar) to a plain Perl script. The resulting script is stored into a buffer provided via a scalar reference in "$p-"{Result}>. The translation is directly done by the original C function Bristled2Plain() from ePerl, so the resulting script is exactly the same as with the stand-alone program eperl. Possible parameters for $p: Script Scalar holding the input script in bristled format. Result Reference to scalar receiving the resulting script in plain Perl format. BeginDelimiter Scalar specifying the begin delimiter. Default is ``"<:"''. EndDelimiter Scalar specifying the end delimiter. Default is ``":>"''. CaseDelimiters Boolean flag indicating if the delimiters are case-sensitive (1=default) or case-insensitive(0). Example: The following code $script = <<'EOT'; foo <: print "bar"; :> quux EOT Parse::ePerl::Translate({ Script => $script, Result => $script, }); translates the script in $script to the following plain Perl format: print "foo "; print "bar"; print " "; print "quux "; COMPILATION: $rc = Parse::ePerl::Precompile($p); This is an optional step between translation and evaluation where the plain Perl script is compiled from ASCII representation to P-code (the internal Perl bytecode). This step is used in rare cases only, for instance from within Apache::ePerl(3) for caching purposes. Possible parameters for $p: Script Scalar holding the input script in plain Perl format, usually the result from a previous Parse::ePerl::Translate(3) call. Result Reference to scalar receiving the resulting code reference. This code can be later directly used via the &$var construct or given to the Parse::ePerl::Evaluate(3) function. Error Reference to scalar receiving possible error messages from the compilation (e.g. syntax errors). Cwd Directory to switch to while precompiling the script. Name Name of the script for informal references inside error messages. Example: The following code Parse::ePerl::Precompile({ Script => $script, Result => $script, }); translates the plain Perl code (see above) in $script to a code reference and stores the reference again in $script. The code later can be either directly used via &$script instead of "eval($script)" or passed to the Parse::ePerl::Evaluate(3) function. EVALUATION: $rc = Parse::ePerl::Evaluate($p); Beside Parse::ePerl::Translate(3) this is the second main function of this package. It is intended to evaluate the result of Parse::ePerl::Translate(3) in a ePerl-like environment, i.e. this function tries to emulate the runtime environment and behavior of the program eperl. This actually means that it changes the current working directory and evaluates the script while capturing data generated on STDOUT/STDERR. Possible parameters for $p: Script Scalar (standard case) or reference to scalar (compiled case) holding the input script in plain Perl format or P-code, usually the result from a previous Parse::ePerl::Translate(3) or Parse::ePerl::Precompile(3) call. Result Reference to scalar receiving the resulting code reference. Error Reference to scalar receiving possible error messages from the evaluation (e.g. runtime errors). ENV Hash containing the environment for %ENV which should be used while evaluating the script. Cwd Directory to switch to while evaluating the script. Name Name of the script for informal references inside error messages. Example: The following code $script = <<'EOT'; print "foo "; print "bar"; print " "; print "quux "; EOT Parse::ePerl::Evaluate({ Script => $script, Result => $script, }); translates the script in $script to the following plain data: foo bar quux ONE-STEP EXPANSION: $rc = Parse::ePerl::Expand($p); This function just combines, Parse::ePerl::Translate(3) and Parse::ePerl::Evaluate(3) into one step. The parameters in $p are the union of the possible parameters for both functions. This is intended as a high-level interface for Parse::ePerl. AUTHOR
Ralf S. Engelschall rse@engelschall.com www.engelschall.com SEE ALSO
eperl(1) Web-References: Perl: perl(1), http://www.perl.com/ ePerl: eperl(1), http://www.engelschall.com/sw/eperl/ perl v5.14.2 2012-04-07 ePerl(3pm)
All times are GMT -4. The time now is 04:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy