<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Linux Remote Server Disk, Memory, Kernel Monitoring Scripting in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/linux-remote-server-disk-memory-kernel-monitoring-scripting/m-p/4619556#M40518</link>
    <description>Just about everything you're looking for is in /proc and a lot of that with collectl.  While you could always run collectl from a script it might be easier to just grab a bunch of data from the same /proc structures.  &lt;A href="http://collectl.sourceforge.net/InputFiles.htmlwill" target="_blank"&gt;http://collectl.sourceforge.net/InputFiles.htmlwill&lt;/A&gt; show you where collectl gets its data from.  As far as other things you can get the kernel version from 'uname' and the mount poins from 'mounts'.  I'm note sure where you could get segfaults, but maybe someone else knows.&lt;BR /&gt;-mark</description>
    <pubDate>Sun, 18 Apr 2010 12:22:32 GMT</pubDate>
    <dc:creator>MarkSeger</dc:creator>
    <dc:date>2010-04-18T12:22:32Z</dc:date>
    <item>
      <title>Linux Remote Server Disk, Memory, Kernel Monitoring Scripting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-remote-server-disk-memory-kernel-monitoring-scripting/m-p/4619555#M40517</link>
      <description>Good day&lt;BR /&gt;&lt;BR /&gt;I have 10+ machines on a network.&lt;BR /&gt;Installed with RHEL 5 operating system.&lt;BR /&gt;&lt;BR /&gt;I am new to scripting ....Can any one help me on writing a script to check on all the machines for&lt;BR /&gt;1) Memory size&lt;BR /&gt;2) Diskspace&lt;BR /&gt;3) Dropped packets on eth0&lt;BR /&gt;4) Disk I/O errors&lt;BR /&gt;5) Kernel Versions&lt;BR /&gt;6) Count of mount points on each node&lt;BR /&gt;7) Segfault errors&lt;BR /&gt;&lt;BR /&gt;if the machine passes above steps should report that the machine is OK&lt;BR /&gt;If any error should alert for system check or failed.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;your co-opertion will be highly apprecieated.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;pleasee advise</description>
      <pubDate>Sun, 18 Apr 2010 09:39:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-remote-server-disk-memory-kernel-monitoring-scripting/m-p/4619555#M40517</guid>
      <dc:creator>raqeeb</dc:creator>
      <dc:date>2010-04-18T09:39:33Z</dc:date>
    </item>
    <item>
      <title>Re: Linux Remote Server Disk, Memory, Kernel Monitoring Scripting</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-remote-server-disk-memory-kernel-monitoring-scripting/m-p/4619556#M40518</link>
      <description>Just about everything you're looking for is in /proc and a lot of that with collectl.  While you could always run collectl from a script it might be easier to just grab a bunch of data from the same /proc structures.  &lt;A href="http://collectl.sourceforge.net/InputFiles.htmlwill" target="_blank"&gt;http://collectl.sourceforge.net/InputFiles.htmlwill&lt;/A&gt; show you where collectl gets its data from.  As far as other things you can get the kernel version from 'uname' and the mount poins from 'mounts'.  I'm note sure where you could get segfaults, but maybe someone else knows.&lt;BR /&gt;-mark</description>
      <pubDate>Sun, 18 Apr 2010 12:22:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-remote-server-disk-memory-kernel-monitoring-scripting/m-p/4619556#M40518</guid>
      <dc:creator>MarkSeger</dc:creator>
      <dc:date>2010-04-18T12:22:32Z</dc:date>
    </item>
  </channel>
</rss>

