"Fossies" - the Fresh Open Source Software Archive
Member "sawdog-2.4/README" (22 Sep 2006, 3694 Bytes) of package /linux/privat/old/sawdog-2.4.tar.gz:
As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard
) with prefixed line numbers.
Alternatively you can here view
the uninterpreted source code file.
1 SAWDOG - Simple Active Watch-DOG
3 Simple: less than 1000 lines of code
4 Active: No need for daemons on the servers
6 SAWDOG - A collection of simple scripts, which informs in case of server outages
7 Copyright 1999-2000 by Christian Gloor
9 This piece of code is distributed under the terms of the GNU General Public License (GPL)
10 You should have received a copy of the GPL (file COPYING) along with this script;
11 if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA
13 Current maintainer: email@example.com, don't hesitate to contact him if you have any questions.
18 Fall 1999: 1.0.0 initial - firstname.lastname@example.org: initial release for internal use only
19 May 2000: 1.2.0 - email@example.com: changed for sms use only
20 May 2000: 2.0.0 phoenix - chgloor: additional features (unknown state, logfile, locking)
21 michi: additional expect scripts (icmp, smb)
22 June 2000: 2.1.0 generic - chgloor: compact notification, one message per server
23 aliases for long server names or ip addresses
24 generic notification (can execute any binaries now)
25 June 2000: 2.2.0 speedup - chgloor: speedup in the expect scripts
26 'required' freature
28 Sept 2006: 2.4.0 webinterface - max added php-based web interface,
29 chgloor: code cleanup
31 This is the README for Version 2.4.x
34 1) Abstract
36 This script was initially written by Christian Gloor. About half a year
37 later, it was adapted for use at DIGICOMP AG, a IT education company located
38 in switzerland.
40 Sawdog consists of a script which informs the sysops of some mission
41 critical servers in the case of a failure. The script executes a given
42 set of small executables, i.e. expect scripts, and if one executable
43 fails, sends an email or a sms to the sysop.
45 2) Installation
47 The main script is sawdog.pl. It can be placed everywhere on the
48 filesystem. However, if you run install.sh, it will place the script in
51 At the moment, the only configuration is done in the sawdog.conf file. If
52 you keep this file not in the current directory, you need to edit the
53 sawdog.pl source file. All file locations are stored in the sawdog.pl file.
55 You can use crontab to start sawdog.pl every 5 minutes, e.g.
57 */5 * * * * root ( cd /usr/local/bin/sawdog/; ./sawdog.pl notify )
60 Sawdog creates a logfile: sawdog.log and a status file: sawdog.status,
61 if they don't exist, sawdog recreates them. Of course sawdog needs write
62 permissions on the working directory.
64 There are some predefined expect scripts for some well known services:
65 ftp, http, icmp, ssh, telnet, and smb. You can easily create your own
66 expect scripts, or use any other executable which returns a return code of
67 zero if it succeeds. Don't forget to contribute your aditions to the main
68 code tree.
70 Files needed:
71 - sawdog.pl the main file
72 - sawdog.conf the config file
73 - services/ this directory is populated by the expect scripts
75 Files recreated, if they don't exist:
76 - sawdog.status in this file the internal state is keept
77 - sawdog.log the logfile
79 3) Usage/Configuration
81 See the postscript/pdf documentation
83 4) To Do
85 Create some more expect scripts for more ports.
86 Build a nice package.
87 Correct spelling and grammar errors in the readme files.
88 Clean up the source