<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Home</title><link>https://sourceforge.net/p/xle/home/Home/</link><description>Recent changes to Home</description><atom:link href="https://sourceforge.net/p/xle/home/Home/feed" rel="self"/><language>en</language><lastBuildDate>Fri, 23 Sep 2011 17:42:57 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/xle/home/Home/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage Home modified by fnds</title><link>https://sourceforge.net/p/xle/home/Home/</link><description>&lt;pre&gt;--- v6 
+++ v7 
@@ -10,6 +10,8 @@
 
 xle is able to check the return code of the command line ($?) and send emails only when an error is detected.
 
+By the way, xle stands for e**X**ecute, **L**og and **E**mail.
+
 Check the [README] for more details.
 
 Installation instructions: [INSTALL]
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fnds</dc:creator><pubDate>Fri, 23 Sep 2011 17:42:57 -0000</pubDate><guid>https://sourceforge.net446ce6821e632adfcf83ce988a038d3ff651e507</guid></item><item><title>WikiPage Home modified by fnds</title><link>https://sourceforge.net/p/xle/home/Home/</link><description>&lt;pre&gt;--- v5 
+++ v6 
@@ -2,7 +2,7 @@
 
 1. do something
 2. send the output to a file
-3. email the file
+3. email someone
 
 In my experience, step 1 (do something) can be very simple, like 'df -h', a script that I wrote , or any other command line. However steps 2 and 3 are kind of like the same every time, with few changes. The code for those additional tasks often ends up being longer and more complex than the original script.
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fnds</dc:creator><pubDate>Fri, 23 Sep 2011 17:39:10 -0000</pubDate><guid>https://sourceforge.net2564ca037bcd3ef955d0f0a73cf55069ecc3377d</guid></item><item><title>WikiPage Home modified by fnds</title><link>https://sourceforge.net/p/xle/home/Home/</link><description>&lt;pre&gt;--- v4 
+++ v5 
@@ -1,4 +1,4 @@
-How many scripts you have written that follow this general flow?
+How many scripts have you written that follow this general flow?
 
 1. do something
 2. send the output to a file
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fnds</dc:creator><pubDate>Fri, 23 Sep 2011 17:37:59 -0000</pubDate><guid>https://sourceforge.netd3612bcdb8aa031c69dd8bb1dfa3c3b43a5e29cf</guid></item><item><title>WikiPage Home modified by fnds</title><link>https://sourceforge.net/p/xle/home/Home/</link><description>&lt;pre&gt;--- v3 
+++ v4 
@@ -4,9 +4,9 @@
 2. send the output to a file
 3. email the file
 
-In my experience, step 1 (do something) can be very simple, like 'df -h', a script that I wrote , or any other command line. However steps 2 and 3 are kind of like the same every time, with few changes. In addition the code for those steps often ends up being longer and more complex than the original script.
+In my experience, step 1 (do something) can be very simple, like 'df -h', a script that I wrote , or any other command line. However steps 2 and 3 are kind of like the same every time, with few changes. The code for those additional tasks often ends up being longer and more complex than the original script.
 
-Instead of repeating the same code over and over, the xle script adds logging and email capability to any command that can be typed at the shell prompt, without any coding. The log files are tagged with a timestamp and saved for future reference.
+Instead of rewriting the same code over and over for every script, the xle script adds logging and email capability to any command that can be typed at the shell prompt, without any coding. The log files are tagged with a timestamp and saved for future reference.
 
 xle is able to check the return code of the command line ($?) and send emails only when an error is detected.
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fnds</dc:creator><pubDate>Fri, 23 Sep 2011 17:37:08 -0000</pubDate><guid>https://sourceforge.net36e182fc10f70106d92273226076c6dc75cfd998</guid></item><item><title>WikiPage Home modified by fnds</title><link>https://sourceforge.net/p/xle/home/Home/</link><description>&lt;pre&gt;--- v2 
+++ v3 
@@ -1,112 +1,19 @@
+How many scripts you have written that follow this general flow?
+
+1. do something
+2. send the output to a file
+3. email the file
+
+In my experience, step 1 (do something) can be very simple, like 'df -h', a script that I wrote , or any other command line. However steps 2 and 3 are kind of like the same every time, with few changes. In addition the code for those steps often ends up being longer and more complex than the original script.
+
+Instead of repeating the same code over and over, the xle script adds logging and email capability to any command that can be typed at the shell prompt, without any coding. The log files are tagged with a timestamp and saved for future reference.
+
+xle is able to check the return code of the command line ($?) and send emails only when an error is detected.
+
+Check the [README] for more details.
+
+Installation instructions: [INSTALL]
+
 [[project_admins]]
 [[download_button]]
 
-
-xle
-====
-fnds
-1/19/11
-
-$Id: README,v 1.2 2011/01/19 17:41:39 fnds Exp $
-
-Intro
-------
-
-xle runs a shell script, checks for errors and sends email to the sysadmin.
-
-It was designed to run from crontab, it runs silently and send all output to $MAINDIR/logs/xle.log
-
-The script was initially written and tested on Red Hat 4. Solaris 9 support was added later. 
-
-Defaults can be changed on $MAINDIR/xle.conf
-
-For usage details, type $MAINDIR/xle
-
-$ cd /home/oracle/xle
-$ ./xle
-
-USAGE: xle [ options ] script arg1 ... argn
-
-Options:
-        -e a    (a)lways sends email (DEFAULT)
-        -e n    (n)ever sends email
-        -e e    sends email only when there was an (e)rror
-        -e s    sends email only when it finishes (s)ucessfully
-
-        -a &lt;alias&gt;      script alias to be used when script name is not descriptive
-        -c &lt;cfg file&gt;   use designated configuration file (full path required)
-        -s &lt;script&gt;     execute &lt;script&gt; file at ./scripts
-        -l              include log file contents in the report sent by email
-        -t &lt;email&gt;      mail to address
-
-        -?              displays help message
-
-$Id: xle,v 1.3 2011/01/20 16:13:55 fnds Exp fnds $
-
-Config file
-------------
-
-Edit the config file to change the sysadmin e-mail, directories, etc
-
-Log files
-----------
-
-The main log file is xle.log kept at $MAINDIR/logs. It keeps a record of
-every script executed by xle.
-
-Every run of each script generates one log file with the script output.
-
-Script log files are also kept at $MAINDIR/logs and are named with script name and a timestamp:
-
-        Example:
-
-        copy2dr.20090510213011.log
-
-        Log file for the copy2dr script that ran on May 10 2009 at 9:30:11 PM.
-
-In addition to log files, a mail file is generated and contains a copy of the
-report sent by email to the sysadmin:
-
-        Example:
-
-        copy2dr.20090510213011.rep
-
-        Same as the example above but ending with .rep
-
-
-crontab examples
------------------
-
-MAINDIR is wherever xle is installed. We use /usr/local/xle
-
-Examples were tested on Red Hat.
-
-- Execute the shell script copy2dr and send email to the sysadmin with results.
-
-        PATH=/usr/local/bin:/bin:/usr/bin:/home/oracle/xle
-        30 21 * * * xle /home/oracle/scripts/backups/copy2dr CPMAXTST
-
-- Execute the script $MAINDIR/scripts/analyze_deltek and send email to the sysadmin.
-  The "-s" option tells it to look for the script at $MAINDIR/scripts.
-
-        PATH=/usr/local/bin:/bin:/usr/bin:/home/oracle/xle
-        30 19 * * * xle -s analyze_deltek
-
-- Execute the shell script copy2dr and send email to the sysadmin only if there are errors, "-e e" option.
-
-        PATH=/usr/local/bin:/bin:/usr/bin:/home/oracle/xle
-        30 21 * * * xle -e e /home/oracle/scripts/backups/copy2dr CPMAXTST
-
-- Execute the shell script copy2dr but never send email, "-e n" option.
-  Log files are still kept at $MAINDIR/logs
-
-        PATH=/usr/local/bin:/bin:/usr/bin:/home/oracle/xle
-        30 21 * * * xle -e e /home/oracle/scripts/backups/copy2dr CPMAXTST
-
-- Execute the script 'dbrun' but use the alias 'analyze_cpweb' to identify it, "-a analyze_cpweb" option
-
-        45 18 * * * xle -a analyze_cpweb /home/oracle/bin/dbrun -b /home/oracle/scripts/analyze_cpweb CPWEB CSTP
-
-
-End
-----
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fnds</dc:creator><pubDate>Fri, 23 Sep 2011 17:35:18 -0000</pubDate><guid>https://sourceforge.net73b8e0419daf5fccaa9acb47e2172a18473274fe</guid></item><item><title>WikiPage Home modified by fnds</title><link>https://sourceforge.net/p/xle/home/Home/</link><description>&lt;pre&gt;--- v1 
+++ v2 
@@ -1,5 +1,112 @@
-Welcome to your wiki!
-
-This is the default page, edit it as you see fit. To add a page simply reference it within brackets, e.g.: [SamplePage].
-
-The wiki uses [Markdown](/p/xle/home/markdown_syntax/) syntax.
+[[project_admins]]
+[[download_button]]
+
+
+xle
+====
+fnds
+1/19/11
+
+$Id: README,v 1.2 2011/01/19 17:41:39 fnds Exp $
+
+Intro
+------
+
+xle runs a shell script, checks for errors and sends email to the sysadmin.
+
+It was designed to run from crontab, it runs silently and send all output to $MAINDIR/logs/xle.log
+
+The script was initially written and tested on Red Hat 4. Solaris 9 support was added later. 
+
+Defaults can be changed on $MAINDIR/xle.conf
+
+For usage details, type $MAINDIR/xle
+
+$ cd /home/oracle/xle
+$ ./xle
+
+USAGE: xle [ options ] script arg1 ... argn
+
+Options:
+        -e a    (a)lways sends email (DEFAULT)
+        -e n    (n)ever sends email
+        -e e    sends email only when there was an (e)rror
+        -e s    sends email only when it finishes (s)ucessfully
+
+        -a &lt;alias&gt;      script alias to be used when script name is not descriptive
+        -c &lt;cfg file&gt;   use designated configuration file (full path required)
+        -s &lt;script&gt;     execute &lt;script&gt; file at ./scripts
+        -l              include log file contents in the report sent by email
+        -t &lt;email&gt;      mail to address
+
+        -?              displays help message
+
+$Id: xle,v 1.3 2011/01/20 16:13:55 fnds Exp fnds $
+
+Config file
+------------
+
+Edit the config file to change the sysadmin e-mail, directories, etc
+
+Log files
+----------
+
+The main log file is xle.log kept at $MAINDIR/logs. It keeps a record of
+every script executed by xle.
+
+Every run of each script generates one log file with the script output.
+
+Script log files are also kept at $MAINDIR/logs and are named with script name and a timestamp:
+
+        Example:
+
+        copy2dr.20090510213011.log
+
+        Log file for the copy2dr script that ran on May 10 2009 at 9:30:11 PM.
+
+In addition to log files, a mail file is generated and contains a copy of the
+report sent by email to the sysadmin:
+
+        Example:
+
+        copy2dr.20090510213011.rep
+
+        Same as the example above but ending with .rep
+
+
+crontab examples
+-----------------
+
+MAINDIR is wherever xle is installed. We use /usr/local/xle
+
+Examples were tested on Red Hat.
+
+- Execute the shell script copy2dr and send email to the sysadmin with results.
+
+        PATH=/usr/local/bin:/bin:/usr/bin:/home/oracle/xle
+        30 21 * * * xle /home/oracle/scripts/backups/copy2dr CPMAXTST
+
+- Execute the script $MAINDIR/scripts/analyze_deltek and send email to the sysadmin.
+  The "-s" option tells it to look for the script at $MAINDIR/scripts.
+
+        PATH=/usr/local/bin:/bin:/usr/bin:/home/oracle/xle
+        30 19 * * * xle -s analyze_deltek
+
+- Execute the shell script copy2dr and send email to the sysadmin only if there are errors, "-e e" option.
+
+        PATH=/usr/local/bin:/bin:/usr/bin:/home/oracle/xle
+        30 21 * * * xle -e e /home/oracle/scripts/backups/copy2dr CPMAXTST
+
+- Execute the shell script copy2dr but never send email, "-e n" option.
+  Log files are still kept at $MAINDIR/logs
+
+        PATH=/usr/local/bin:/bin:/usr/bin:/home/oracle/xle
+        30 21 * * * xle -e e /home/oracle/scripts/backups/copy2dr CPMAXTST
+
+- Execute the script 'dbrun' but use the alias 'analyze_cpweb' to identify it, "-a analyze_cpweb" option
+
+        45 18 * * * xle -a analyze_cpweb /home/oracle/bin/dbrun -b /home/oracle/scripts/analyze_cpweb CPWEB CSTP
+
+
+End
+----
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fnds</dc:creator><pubDate>Fri, 23 Sep 2011 15:59:59 -0000</pubDate><guid>https://sourceforge.net93de799abb879cee121cc03c851bb2ecdaa299d4</guid></item><item><title>WikiPage Home modified by FNdS</title><link>https://sourceforge.net/p/xle/home/Home/</link><description>Welcome to your wiki!

This is the default page, edit it as you see fit. To add a page simply reference it within brackets, e.g.: [SamplePage].

The wiki uses [Markdown](/p/xle/home/markdown_syntax/) syntax.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">FNdS</dc:creator><pubDate>Fri, 23 Sep 2011 15:42:28 -0000</pubDate><guid>https://sourceforge.net3a7c7b939d93233b7c370f544b7f35a300c502a5</guid></item></channel></rss>