[lwatch-cvs] files/doc lwatch.conf.sgml,1.3,1.4 lwatch.sgml,1.18,1.19
Brought to you by:
arturcz
|
From: Karolina G. <ca...@us...> - 2004-08-11 13:37:14
|
Update of /cvsroot/lwatch/files/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27674 Modified Files: lwatch.conf.sgml lwatch.sgml Log Message: proofreading Index: lwatch.conf.sgml =================================================================== RCS file: /cvsroot/lwatch/files/doc/lwatch.conf.sgml,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** lwatch.conf.sgml 11 Aug 2004 12:06:24 -0000 1.3 --- lwatch.conf.sgml 11 Aug 2004 13:37:04 -0000 1.4 *************** *** 7,11 **** <!-- ! This file is part of the LogWatcher tool. Copyright (C) 2002,2003,2004 Artur Robert Czechowski --- 7,11 ---- <!-- ! This file is a part of the LogWatcher tool. Copyright (C) 2002,2003,2004 Artur Robert Czechowski *************** *** 18,22 **** The LogWatcher is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of ! MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. --- 18,22 ---- The LogWatcher is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of ! MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. *************** *** 65,69 **** <refsect2> <title>General options</title> ! <para><option>cfg_ver</option> - this is obligatory variable and it must be placed as a first option in config file (note: although it is not enforced now, it shall be in next release of lwatch). This variable contains version of configuration file syntax. Current manual describes version 1.</para> <para><option>date_color</option> - default color of date part</para> <para><option>host_color</option> - default color of hostname part</para> --- 65,69 ---- <refsect2> <title>General options</title> ! <para><option>cfg_ver</option> - this is obligatory variable and it must be placed as the first option in config file (note: although it is not enforced now, it shall be in next release of lwatch). This variable contains version of configuration file syntax. Current manual describes version 1.</para> <para><option>date_color</option> - default color of date part</para> <para><option>host_color</option> - default color of hostname part</para> *************** *** 72,76 **** <para><option>input_file</option> - where lwatch is reading data from, built-in default is &infile;, could be overwriten with command line option <option>-i</option></para> <para><option>output_file</option> - where lwatch output colored data; built-in default is stdout (-), could be overwriten with command line option <option>-o</option></para> ! <para><option>show_unparsed</option> - by default lwatch ignores lines which cannot be splitted into date, host, service and message, set this variable to yes if you like to see those lines; it is the same as command line option <option>-s</option></para> </refsect2> --- 72,77 ---- <para><option>input_file</option> - where lwatch is reading data from, built-in default is &infile;, could be overwriten with command line option <option>-i</option></para> <para><option>output_file</option> - where lwatch output colored data; built-in default is stdout (-), could be overwriten with command line option <option>-o</option></para> ! <para><option>show_unparsed</option> - by default lwatch ignores ! lines which cannot be splitted into date, host, service and message, set this variable to yes if you would like to see those lines; it is the same as command line option <option>-s</option></para> </refsect2> *************** *** 82,87 **** <refsect2> <title>Matching patterns</title> ! <para>There is hidden The Power of Lwatch. You can match input lines again PCRE (Perl Compatible Regular Expression) and change output depends on matching. You can read more about PCRE in pcrepattern(3) (from libpcre) or in perlre(1) (from perl).</para> ! <para>There are two way to define matchin pattern/action. First one is the simple one. Just pattern and one action: <literallayout> /regexp/ action --- 83,88 ---- <refsect2> <title>Matching patterns</title> ! <para>There The True Power of Lwatch is hidden. You can match input lines against PCRE (Perl Compatible Regular Expression) and change output depends on matching. You can read more about PCRE in pcrepattern(3) (from libpcre) or in perlre(1) (from perl).</para> ! <para>There are two ways to define matching pattern/action. First one is the simple one. Just pattern and one action: <literallayout> /regexp/ action *************** *** 97,101 **** </literallayout> </para> ! <para>There is one important thing which you should remember. There is no need to quote / (slash) if you use it inside regexp pattern. For example: <literallayout> --- 98,102 ---- </literallayout> </para> ! <para>There is one important thing you should remember. There is no need to quote / (slash) if you use it inside regexp pattern. For example: <literallayout> *************** *** 106,111 **** </literallayout> </para> ! <para>For every input line message part is matched against all defined patterns, from top to bottom. For every matched ! pattern attached actions are runned until <option>exit</option> is not specified (see below).</para> </refsect2> --- 107,111 ---- </literallayout> </para> ! <para>For every input line message part is matched against all defined patterns, from top to bottom. For every matched pattern attached actions are run until <option>exit</option> is specified (see below).</para> </refsect2> Index: lwatch.sgml =================================================================== RCS file: /cvsroot/lwatch/files/doc/lwatch.sgml,v retrieving revision 1.18 retrieving revision 1.19 diff -C2 -d -r1.18 -r1.19 *** lwatch.sgml 11 Aug 2004 12:06:24 -0000 1.18 --- lwatch.sgml 11 Aug 2004 13:37:04 -0000 1.19 *************** *** 170,174 **** in your syslog.conf. Create appropriate fifo and restart syslog, then run lwatch. You can also run lwatch before starting syslog. ! If you dont know how to create named fifo see mknod(1) for details. </para> --- 170,174 ---- in your syslog.conf. Create appropriate fifo and restart syslog, then run lwatch. You can also run lwatch before starting syslog. ! If you don't know how to create named fifo see mknod(1) for details. </para> *************** *** 190,194 **** Lwatch does not support reading from regular files. If you really need this functionality use following command: <literallayout>tail -f /path/to/filename | &bin; -i-</literallayout> ! It could be subject of change in the future. </para> </refsect1> --- 190,194 ---- Lwatch does not support reading from regular files. If you really need this functionality use following command: <literallayout>tail -f /path/to/filename | &bin; -i-</literallayout> ! It could be subject to change in the future. </para> </refsect1> *************** *** 223,230 **** <title>NOTE FROM AUTHOR</title> <para>I have writen this tool for my own needs because perl tools, however flexible, eated a lot of memory and CPU. ! I have found it useful and I share it with the Open Source Community. But stil developing of this software is driven ! by my own needs. So, you could except next release in a year or two ;)</para> ! <para>It would be really nice if you could find some time and spare it for rate this project on FreshMeat (see RESOURCES). Comments are welcomed too. I cannot promise that I will add new features to lwatch immediatly but any positive feedback will raise my motivation level up.</para> ! <para>Thank in advance for your time.</para> </refsect1> --- 223,234 ---- <title>NOTE FROM AUTHOR</title> <para>I have writen this tool for my own needs because perl tools, however flexible, eated a lot of memory and CPU. ! I have found it useful and I share it with the Open Source ! Community. But still, developing of this software is driven ! by my own needs. So, you could expect next release in a year or two ;)</para> ! <para>It would be really nice if you could find some time and spare ! it for rating this project on FreshMeat (see RESOURCES). Comments ! are welcome too. I cannot promise that I will add new features to ! lwatch immediately but any positive feedback will raise my motivation level up.</para> ! <para>Thank you in advance for your time.</para> </refsect1> |