removed irrelevant documentation from POD docs

diff --git a/contrib/plugins/spong-server/data_sendmsg b/contrib/plugins/spong-server/data_sendmsg
index fe2c64d2ca8de2a00de278a3dd48163c08552043..508c6406dd4c1d21d1ea4079a2c1e5bfe3aea385 100644 (file)
--- a/contrib/plugins/spong-server/data_sendmsg
+++ b/contrib/plugins/spong-server/data_sendmsg
@@ -17,7 +17,7 @@ upper level Spong configurations.
 # spong-servers. Typical use would be to setup Spong regions and feeding all
 # regional status messages to a top level server.
 
-# $Id: data_sendmsg,v 1.1 2000/09/14 17:01:09 sljohnson Exp $
+# $Id: data_sendmsg,v 1.2 2001/05/07 14:48:17 sljohnson Exp $
 
 use Spong::Status "0.02";
 
@@ -105,15 +105,6 @@ or Perl regulare expressions.
 L<spong-server>, L<spong.conf>,
 L<Spong Developer Guide|developer-guide>
 
-=head1 NOTES
-
-The B<check_interfaces> module use SNMP to poll a host. It retrieves the
-B<ifIndex>, B<ifDesc>, B<ifType>, B<ifAdminStatus>, and  B<ifOperStatus> fields
-for every entry in the B<ifTable> table. The module then scans all of all of
-the network interfaces inretrieved from the table. Any interface that is
-administratively up and is not operationally up will result in an critical
-status (red) being return.
-
 =head1 RESTRICTIONS
 
 B<data_sendmsg> uses the C<Spong::Status> library module to work.  It uses the