Sponsored Content
Full Discussion: Safely parsing parameters
Top Forums Shell Programming and Scripting Safely parsing parameters Post 302403158 by Corona688 on Thursday 11th of March 2010 04:57:25 PM
Old 03-11-2010
You're missing the point. I need to handle arbitrary strings. So what if your string doesn't have backticks?
 

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
xstr(1) 						      General Commands Manual							   xstr(1)

Name
       xstr - extract strings from C program

Syntax
       xstr [-c] [-] [file]

Description
       The  command maintains a file strings into which strings in component parts of a large program are hashed.  These strings are replaced with
       references to this common area.	This serves to implement shared constant strings, most useful if they are also read-only.

       The command
       xstr -c name

       will extract the strings from the C source in name, replacing string references by expressions of the form (&xstr[number]) for some number.
       An  appropriate declaration of is prepended to the file.  The resulting C text is placed in the file x.c, to then be compiled.  The strings
       from this file are placed in the strings data base if they are not there already.  Repeated strings  and  strings  which  are  suffices	of
       existing strings do not cause changes to the data base.

       After all components of a large program have been compiled a file xs.c declaring the common space can be created by a command of the form
       xstr

       This xs.c file should then be compiled and loaded with the rest of the program.	If possible, the array can be made read-only (shared) sav-
       ing space and swap overhead.

       The command can also be used on a single file.  A command
       xstr name

       creates files x.c and xs.c as before, without using or affecting any strings file in the same directory.

       It may be useful to run after the C preprocessor if any macro definitions yield strings or if there  is	conditional  code  which  contains
       strings	which may not, in fact, be needed.  The command reads from its standard input when the argument `-' is given.  An appropriate com-
       mand sequence for running after the C preprocessor is:
       cc -E name.c | xstr -c -
       cc -c x.c
       mv x.o name.o

       The command does not touch the file strings unless new items are added, thus can avoid remaking xs.o unless truly necessary.

Options
       -  Reads stdin.

       -c Extracts strings from specified C source (next argument).

Restrictions
       If a string is a suffix of another string in the data base, but the shorter string is seen first by both strings will be placed in the data
       base, when just placing the longer one there will do.

Files
       strings	      Data base of strings
       x.c	 Massaged C source
       xs.c	 C source for definition of array `xstr'
       /tmp/xs*  Temp file when `xstr name' doesn't touch strings

See Also
       mkstr(1)

																	   xstr(1)
All times are GMT -4. The time now is 11:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy