On 11/03/14 16:16, Les Mikesell wrote: > On Tue, Mar 11, 2014 at 9:49 AM, Toralf Lund <toralf.lund at pgs.com> wrote: >>> I think you should build a >>> monitoring system (nagios, xymon, opennms, several others or perhaps >>> your own if you're feeling far too adventurous) instead. right now >>> all you care about is disk space, but eventually someone will want to >>> also check for certain processes, open ports, logfile entries, >>> something and you could spend the time now to put in the hooks for >>> more advanced things and get people in the habit of checking a >>> monitoring system on a regular basis. >> In general, that might make sense, but please consider the fact that I'm >> not talking about a "general" server system. It's a machine dedicated to >> running a "server" component on one specific software package, and will >> only ever be contacted by a handful of "display" machines running a GUI >> component of the same piece of software. > Then you need to look at the features of the specific GUI and its > transport to the server to see what options it provides for popup > messages. I can easily add a check to software itself. But like I said, I want to avoid re-inventing the wheel. So if there is something built into the system that will do the job for me... > Personally, I'd still recommend something more general > that would generate email or text message alerts to the right set of > people. It is fairly rare for 'users' to be interested in fixing > system problems and even if that happens to be the case now for this > particular box it may not always be. Trust me, this is a highly customised setup with very special users, and this won't change just like that. A more general system is not an entirely bad idea, but I think it would only make sense if implemented at a larger scale based on a system-wide policy (there is much else going on in the same network.) Which I'm not sure will happen right now... - Toralf > This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.