RE: Snort and memory

["Mayers, Philip J" <p.mayers () ic ac uk>]

And on that note - an obvious suggestion for barnyard is "transaction
batching" - i.e. database insert are a lot faster with many-per-transaction,
but inserting 600meg of data inside a transaction will likely deadlock the
database for a long time. Maybe a transact commit every 100 inserts?

Regards,
Phil

+------------------------------------------+
| Phil Mayers                              |
| Network & Infrastructure Group           |
| Information & Communication Technologies |
| Imperial College                         |
+------------------------------------------+

-----Original Message-----
From: Martin Roesch [mailto:roesch () sourcefire com]
Sent: 29 August 2001 01:52
To: Scott Nursten
Cc: Marcin Zurakowski; snort-users () lists sourceforge net
Subject: Re: [Snort-users] Snort and memory


Stop running the database output plugin and see if it continues to leak
memory.  You can log to a binary file with the -b switch and
periodically read the log file into the database by running it back thru
Snort with the -r switch.  This could work as a temporary solution until
we get Barnyard working.

     -Marty

_______________________________________________
Snort-users mailing list
Snort-users () lists sourceforge net
Go to this URL to change user options or unsubscribe:
http://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users