Use of cp in a script Post: 302582010

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

create a shell script that calls another script and and an awk script

Hi guys I have a shell script that executes sql statemets and sends the output to a file.the script takes in parameters executes sql and sends the result to an output file. #!/bin/sh echo " $2 $3 $4 $5 $6 $7 isql -w400 -U$2 -S$5 -P$3 << xxx use $4 go print"**Changes to the table...

2. Shell Programming and Scripting

Script will keep checking running status of another script and also restart called script at night

I am using blow script :-- #!/bin/bash FIND=$(ps -elf | grep "snmp_trap.sh" | grep -v grep) #check snmp_trap.sh is running or not if then # echo "process found" exit 0; else echo "process not found" exec /home/Ketan_r /snmp_trap.sh 2>&1 & disown -h ...

3. UNIX for Dummies Questions & Answers

Calling a script from master script to get value from called script

I am trying to call a script(callingscript.sh) from a master script(masterscript.sh) to get string type value from calling script to master script. I have used scripts mentioned below. #masterscript.sh ./callingscript.sh echo $fileExist #callingscript.sh echo "The script is called"...

4. Shell Programming and Scripting

Shell script works fine as a standalone script but not as part of a bigger script

Hello all, I am facing a weird issue while executing a code below - #!/bin/bash cd /wload/baot/home/baotasa0/sandboxes_finance/ext_ukba_bde/pset sh UKBA_publish.sh UKBA 28082015 3 if then echo "Param file conversion for all the areas are completed, please check in your home directory"...

5. Shell Programming and Scripting

How to block first bash script until second bash script script launches web server/site?

I'm new to utilities like socat and netcat and I'm not clear if they will do what I need. I have a "compileDeployStartWebServer.sh" script and a "StartBrowser.sh" script that are started by emacs/elisp at the same time in two different processes. I'm using Cygwin bash on Windows 10. My...

LEARN ABOUT DEBIAN

mkdoc::xml::treebuilder

MKDoc::XML::TreeBuilder(3pm)				User Contributed Perl Documentation			      MKDoc::XML::TreeBuilder(3pm)

NAME

       MKDoc::XML::TreeBuilder - Builds a parsed tree from XML data

SYNOPSIS

	 my @top_nodes = MKDoc::XML::TreeBuilder->process_data ($some_xml);

SUMMARY

       MKDoc::XML::TreeBuilder uses MKDoc::XML::Tokenizer to turn XML data into a parsed tree. Basically it smells like an XML parser, looks like
       an XML parser, and awfully overlaps with XML parsers.

       But it's not an XML parser.

       XML parsers are required to die if the XML data is not well formed.  MKDoc::XML::TreeBuilder doesn't give a rip: it'll parse whatever as
       long as it's good enough for it to parse.

       XML parsers expand entities. MKDoc::XML::TreeBuilder doesn't.  At least not yet.

       XML parsers generally support namespaces. MKDoc::XML::TreeBuilder doesn't - and probably won't.

DISCLAIMER

       This module does low level XML manipulation. It will somehow parse even broken XML and try to do something with it. Do not use it unless
       you know what you're doing.

API

   my @top_nodes = MKDoc::XML::Tokenizer->process_data ($some_xml);
       Returns all the top nodes of the $some_xml parsed tree.

       Although the XML spec says that there can be only one top element in an XML file, you have to take two things into account:

       1. Pseudo-elements such as XML declarations, processing instructions, and comments.

       2. MKDoc::XML::TreeBuilder is not an XML parser, it's not its job to care about the XML specification, so having multiple top elements is
       just fine.

   my $tokens = MKDoc::XML::Tokenizer->process_data ('/some/file.xml');
       Same as MKDoc::XML::TreeBuilder->process_data ($some_xml), except that it reads $some_xml from '/some/file.xml'.

Returned parsed tree - data structure
       I have tried to make MKDoc::XML::TreeBuilder look enormously like HTML::TreeBuilder.  So most of this section is stolen and slightly
       adapted from the HTML::Element man page.

       START PLAGIARISM HERE

       It may occur to you to wonder what exactly a "tree" is, and how it's represented in memory.  Consider this HTML document:

	 <html lang='en-US'>
	   <head>
	     <title>Stuff</title>
	     <meta name='author' content='Jojo' />
	   </head>
	   <body>
	    <h1>I like potatoes!</h1>
	   </body>
	 </html>

       Building a syntax tree out of it makes a tree-structure in memory that could be diagrammed as:

			    html (lang='en-US')
			     / 
			   /	 
			 /	   
		       head	   body
		      /	       
		    /	 		 
		  /	   		   
		title	  meta		    h1
		 |	 (name='author',     |
	      "Stuff"	 content='Jojo')    "I like potatoes"

       This is the traditional way to diagram a tree, with the "root" at the top, and it's this kind of diagram that people have in mind when they
       say, for example, that "the meta element is under the head element instead of under the body element".  (The same is also said with
       "inside" instead of "under" -- the use of "inside" makes more sense when you're looking at the HTML source.)

       Another way to represent the above tree is with indenting:

	 html (attributes: lang='en-US')
	   head
	     title
	       "Stuff"
	     meta (attributes: name='author' content='Jojo')
	   body
	     h1
	       "I like potatoes"

       Incidentally, diagramming with indenting works much better for very large trees, and is easier for a program to generate.  The $tree->dump
       method uses indentation just that way.

       However you diagram the tree, it's stored the same in memory -- it's a network of objects, each of which has attributes like so:

	 element #1:  _tag: 'html'
		      _parent: none
		      _content: [element #2, element #5]
		      lang: 'en-US'

	 element #2:  _tag: 'head'
		      _parent: element #1
		      _content: [element #3, element #4]

	 element #3:  _tag: 'title'
		      _parent: element #2
		      _content: [text segment "Stuff"]

	 element #4   _tag: 'meta'
		      _parent: element #2
		      _content: none
		      name: author
		      content: Jojo

	 element #5   _tag: 'body'
		      _parent: element #1
		      _content: [element #6]

	 element #6   _tag: 'h1'
		      _parent: element #5
		      _content: [text segment "I like potatoes"]

       The "treeness" of the tree-structure that these elements comprise is not an aspect of any particular object, but is emergent from the
       relatedness attributes (_parent and _content) of these element-objects and from how you use them to get from element to element.

       STOP PLAGIARISM HERE

       This is pretty much the kind of data structure MKDoc::XML::TreeBuilder returns. More information on different nodes and their type is
       available in MKDoc::XML::Token.

NOTES

       Did I mention that MKDoc::XML::TreeBuilder is NOT an XML parser?

AUTHOR

       Copyright 2003 - MKDoc Holdings Ltd.

       Author: Jean-Michel Hiver

       This module is free software and is distributed under the same license as Perl itself. Use it at your own risk.

SEE ALSO

       MKDoc::XML::Token MKDoc::XML::Tokenizer

perl v5.10.1							    2004-10-06					      MKDoc::XML::TreeBuilder(3pm)