Your message dated Wed, 9 Aug 2006 00:53:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing ancient (tagged woody) bugs
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: snort
Version: 1.8p1-1
Severity: important
It seems to be very difficult to keep snort running for more than 24 hours at a
time on my Apple Macintosh Cube G4. It has 1.5GB RAM and snort is listening on
the
built-in GMAC Ethernet. I've looked at all of the log files, and the best I can
find is a message indicating that eth0 left promiscuous mode -- typically the
only way that I can discover that the daemon has crashed. This is at times
distinct
from the regular snort restart.
-- System Information
Debian Release: 3.0
Architecture: powerpc
Kernel: Linux aglaia 2.4.17-xfs #1 Mon Feb 4 19:05:50 PST 2002 ppc
Locale: LANG=C, LC_CTYPE=C
Versions of packages snort depends on:
ii adduser 3.45 Add and remove users and groups
ii debconf 1.0.25 Debian configuration management sy
ii libc6 2.2.4-7 GNU C Library: Shared libraries an
ii libpcap0 0.6.2-2 System interface for user-level pa
ii snort-common 1.8p1-1 Flexible NIDS (Network Intrusion D
ii snort-rules-default [snort-ru 1.8p1-1 Flexible NIDS (Network Intrusion D
ii sysklogd [syslogd] 1.4.1-10 System Logging Daemon
ii sysklogd [system-log-daemon] 1.4.1-10 System Logging Daemon
ii unixodbc 2.1.1-1 ODBC tools libraries
--- End Message ---
--- Begin Message ---
Hi,
This bug has been open for quite a long time and it is tagged 'woody'. As the
latest Debian release 3.1 'sarge' has been available since last year and this
bugs do not seem to be present there I'm closing this bug.
Please reopen the bug if you have evidence that this bug is still present in
newer versions of the package. Any additional information would also be
really useful.
Thanks
Javier
signature.asc
Description: Digital signature
--- End Message ---
