<div dir="ltr">I have a G1 model B that's been running Nagios on Red Sleeve 6.1 for a couple of years. The checks work fine, but they just test remote services; I wouldn't try anything that requires a lot of local processing. I can't think of any reason that the processor architecture would come into play. What was painful for me is how long it took to actually change the configuration. I ultimately used a VM, and I use the Pi to check the VM and host. The G2 says that the processor is 200 MHz faster, and it has twice as much RAM, so it might be tolerable now.<div><br></div><div>What's the LAMP part of your question?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 9, 2015 at 11:14 PM, <span dir="ltr"><<a href="mailto:foo7775@comcast.net" target="_blank">foo7775@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Arial;font-size:12pt;color:#000000"><div>Hey guys (& gals),<br></div><div><br></div><div> I'm giving serious thought to setting up a "latest generation" Raspberry Pi as a headless server running Nagios so that I can quickly & easily check up on one segment of my home network when/if the mood strikes me. Has anyone on this list set up Nagios on a Pi system, & if so, do you have any suggestions, or any "gotchas" to watch out for?? (Aside from the obvious ARM architecture as opposed to x86/64...)<br></div><div><br></div><div> It may be worth noting that I will be setting it up to boot RedSleeve (RHEL-derived) instead of the Debian-derived OS that it comes with...<br></div><div><br></div><div>Thanks in advance,<br></div><div><br></div><div>T.<br></div></div></div><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>