Safely parsing parameters Post: 302590155

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...

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...

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. 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...

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 /...

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 ...

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...

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...

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...

LEARN ABOUT DEBIAN

hotswaprc

HOTSWAPRC(5)							File Formats Manual						      HOTSWAPRC(5)

NAME

       hotswaprc - configuration file for  hotswap

DESCRIPTION

       /etc/hotswaprc is the global configuration file for the hotswap utility.

       It  allows system administrators to specify arbitrary shell scripts to be run after a device is inserted, as well as before and after it is
       removed. Scripts are selected according to the model name retrieved from the device. This is particularly helpful for automatic	configura-
       tion of CD-RW drives, which require SCSI emulation and bypass normal access via the IDE subsystem.

       hotswaprc  is  implemented  as  an  Extensible Mark-up Language (XML) application.  XML documents are structured using elements of the form
       <tag-name> content <tag-name>. A Document Type Definition (DTD) describes the possible content of each element.

       Please refer to the XML specification for more information. The hotswap distribution also contains an example file,  doc/hotswaprc.example,
       which includes the DTD for the configuration file format.

ELEMENTS

       <hotswap>
	      This is the root element of the document. Each valid hotswaprc must contain exactly one <hotswap> element. The <hotswap> element may
	      contain an arbitrary number of <device> elements.

       <device>
	      The configuration file contains one <device> element for every device for which scripts are defined. The <device>  element  is  com-
	      posed of the following elements in this order: <name>, <post-insert>, <pre-remove>, <post-remove>. All but <name> are optional.

       <name> The content of this element is the model identification string of the IDE device the current <device> element refers to.

       <post-insert>
	      Contains the shell script that is to be executed after the device has been inserted and registered with the kernel.

       <pre-remove>
	      Contains the shell script that is to be run before hotswap attempts to unregister the device.

       <post-remove>
	      Contains the shell script that is to be run after the device had been unregistered.

REPORT BUGS

       Report bugs to t.stadelmann1@physics.ox.ac.uk.

AUTHOR

       Written by Tim Stadelmann.

SEE ALSO

       hotswap(1), xhotswap(1).

COPYRIGHT

       Copyright (c) 2002-2003 Tim Stadelmann.

       Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License (GPL), Version 2 or
       any later version published by the Free Software Foundation.

								26th November 2002						      HOTSWAPRC(5)