|
Bugzilla – Full Text Bug Listing |
| Summary: | arpwatch does only support one interface | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Christian Andretzky <Christian.Andretzky> |
| Component: | Network | Assignee: | Roman Drahtmueller <draht> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | forgotten_PQKW3NFi6R, novell.com |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Andretzky
2006-02-08 08:37:11 UTC
Sounds like an enhancement. Quick and drity fix for this:
[part of /etc/init.d/arpwatch ]
.
.
.
case "$1" in
start)
echo -n "Starting arpwatch"
for interface in $ARPWATCH_INTERFACE; do
# ARPWATCH_ARGS="$ARPWATCH_ARGS -i $interface"
ARPLOGFILE=/var/lib/arpwatch/arp.${interface}.dat
touch $ARPLOGFILE
#startproc $ARPWATCH $ARPWATCH_ARGS -f $ARPLOGFILE -i $interface
$ARPWATCH $ARPWATCH_ARGS -f $ARPLOGFILE -i $interface
done
rc_status -v
;;
stop)
echo -n "Shutting down arpwatch"
killproc -TERM $ARPWATCH
rc_status -v
;;
.
.
.
startproc cannot be used because we try to start more than one instance of arpwatch.
Fixed for 11.1/SLES11.
case "$1" in
start)
ARPWATCH_STARTED=0
echo -n "Starting arpwatch"
for interface in $ARPWATCH_INTERFACE; do
if /sbin/ifstatus $interface > /dev/null 2>&1; then
DATFILE=/var/lib/arpwatch/arp.dat.$interface
if [ ! -f "$DATFILE" ]; then
/bin/cp -a /var/lib/arpwatch/arp.dat $DATFILE
fi
TEMP_ARGS="$ARPWATCH_ARGS -i $interface -f $DATFILE"
$ARPWATCH $TEMP_ARGS
ARPWATCH_STARTED=$(( $ARPWATCH_STARTED + 1 ))
else
echo "${attn} interface ${warn}$interface ${attn} is not ready.${norm}"
fi
done
if [ "$ARPWATCH_STARTED" = 0 ]; then
startproc $ARPWATCH $ARPWATCH_ARGS
fi
rc_status -v
;;
stop)
...
*** Bug 245181 has been marked as a duplicate of this bug. *** *** Bug 337130 has been marked as a duplicate of this bug. *** |