path: root/inotail.c
diff options
Diffstat (limited to 'inotail.c')
1 files changed, 0 insertions, 6 deletions
diff --git a/inotail.c b/inotail.c
index 9dae0b8..2756dd2 100644
--- a/inotail.c
+++ b/inotail.c
@@ -38,21 +38,15 @@
#include "inotail.h"
#define PROGRAM_NAME "inotail"
-/* inotify event buffer length for one file */
-#define INOTIFY_BUFLEN (4 * sizeof(struct inotify_event))
/* Print header with filename before tailing the file? */
static char verbose = 0;
/* Tailing relative to begin or end of file */
static char from_begin = 0;
/* Follow the file by name or by fd */
static enum follow_mode follow = FOLLOW_DESCRIPTOR;
/* Retry accessing the file if it got lost (e.g. deleted, moved) */
static char retry = 0;
/* Number of ignored files */
static int n_ignored = 0;
multicast groups
The range of addresses between and inclusive, is reserved for the use of routing protocols and other low-level topology discovery or maintenance protocols, such as gateway discovery and group membership reporting. Multicast routers should not forward any multicast datagram with destination addresses in this range, regardless of its TTL. Currently, IGMP reports are generated for this reserved range of addresses even though a router will ignore this information since it has no purpose. However, the presence of reserved group addresses in an IGMP membership report uses up network bandwidth and can also obscure addresses of interest when inspecting membership reports using packet inspection or debug messages. Although the RFCs for the various version of IGMP (e.g.RFC 3376 for v3) do not specify that the reserved addresses be excluded from membership reports, it should do no harm in doing so. In particular there should be no adverse effect in any IGMP snooping functionality since 224.0.0.x is specifically excluded as per RFC 4541 (IGMP and MLD Snooping Switches Considerations) section 2.1.2. Data Forwarding Rules: 2) Packets with a destination IP (DIP) address in the 224.0.0.X range which are not IGMP must be forwarded on all ports. IGMP reports for local multicast groups can now be optionally inhibited by means of a system control variable (by setting the value to zero) e.g.: echo 0 > /proc/sys/net/ipv4/igmp_link_local_mcast_reports To retain backwards compatibility the previous behaviour is retained by default on system boot or reverted by setting the value back to non-zero e.g.: echo 1 > /proc/sys/net/ipv4/igmp_link_local_mcast_reports Signed-off-by: Philip Downey <> Signed-off-by: David S. Miller <>
Diffstat (limited to 'include/linux/igmp.h')
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/igmp.h b/include/linux/igmp.h