![dedup avisynth dedup avisynth](http://www.infognition.com/super_resolution_avisynth/avssr400.jpg)
It still is pretty simple with a simple interface. Overall I think that ‘mon’ is much more complex, but only to add features, and it doesn’t have a lot of features I wouldn’t use.
![dedup avisynth dedup avisynth](https://i.imgur.com/gGemWKU.png)
A script have many states, not just “success” or “failure”. If it returned success, the status line would display in green for success (on the web interface), or red for failure. The script could return with a success (0) or non-success status code.For example the monitor “ping” checks whether a host is pingable. Monitors can be anything, but several useful ones are provided in /usr/lib/mon/mon.d (on debian).Or, I use ‘ monshow‘, which is similar but in a text format. All output can be displayed in a simple html table, with the name of the service, the status (with color coding), the time of last and next run, and a short output line.The hostname(s) are added to the command line automatically. For each service, it runs a single-line command (monitor) with arguments.The list of 30 services is defined in /etc/mon/con.cf.The reason all scripts ran every time, is to prevent a failure mode where the information could ever be stale without me noticing.If the script took too long to run, it would be highlighted yellow. For example, “ ping?” checks whether a host is pingable. Scripts can be anything, but I wrote several utility functions to be called from scripts.If it failed, the line would be highlighted red for failure. If it returned success, that status line would display in green for success.
![dedup avisynth dedup avisynth](http://www.padeditor.com/uploads/images/1-year-advertisement-service.png)
All output is displayed in a simple html table, with the name of the service, the status (with color coding), and a short output line.For each service, it ran a short script, with no command line arguments.The list of services is one-per-file in a the services.d directory.Then, the status page would (live) kick of about 30 parallel jobs, to check the status of 30 services The old service, ‘ simple-status‘ worked as follows: ‘mon’ adds many features over my own system, but still has a very bare-bones feeling. It is targeted at working system administrators. I am replacing it with a linux monitoring daemon, mon, which I recommend. I had previously hand-rolled a status monitor,, which I am in the process of replacing ( new version).