aboutsummaryrefslogtreecommitdiffstats
path: root/ringbuffer.h
AgeCommit message (Collapse)AuthorFilesLines
2010-08-28As mentioned on the users-mailinglist[1], it could be useful to have groups ↵Sake Blok1-1/+1
read access to the ringbuffer that dumpcap creates. That way, a group of people can access the capture files without having to use root access. [1] http://www.wireshark.org/lists/wireshark-users/201008/msg00235.html svn path=/trunk/; revision=33978
2010-05-27Set RINGBUFFER_MAX_NUM_FILES to 100000. Use it to generate file names.Gerald Combs1-4/+6
Add RINGBUFFER_WARN_NUM_FILES and use it to print a warning. Print warnings when we change the number of ringbuffer files. svn path=/trunk/; revision=32998
2010-05-14If something is only supposed to be included if we have libpcap, don'tGuy Harris1-4/+0
put #ifdef HAVE_LIBPCAP in it. Add multiple-inclusion protection to capture_errs.h. svn path=/trunk/; revision=32803
2009-04-26Make ringbuffer.[ch] file format agnostic.Michael Tüxen1-3/+2
Move write routines to dumpcap.c This is a preparation for pcapng support. svn path=/trunk/; revision=28155
2006-05-21name changeRonnie Sahlberg1-2/+2
svn path=/trunk/; revision=18197
2006-04-29Have the ring buffer routines take a pointer to a "bytes written" countGuy Harris1-2/+4
as an argument, rather than keeping the count to themselves, so the count kept by the capturing program can be updated correctly - including getting reset when files are switched. Fixes bug 895. svn path=/trunk/; revision=18032
2006-03-04When capturing, we only support writing to libpcap files. Given that,Guy Harris1-4/+3
bypass Wiretap; that means we don't have to run the packet through wtap_process_pcap_packet() and then undo that conversion in Wiretap if we're just going to write it out, shortening the code path. svn path=/trunk/; revision=17461
2005-12-05requested by Cory Perry:Ulf Lamping1-1/+2
increase the maximum number of ringbuffer files from 1024 to 10000. svn path=/trunk/; revision=16690
2005-03-28major capture engine rework: use two task model for EVERY capture modeUlf Lamping1-0/+1
rework of the -b command line parameter (for Ethereal and Tethereal) svn path=/trunk/; revision=13949
2005-02-03prevent ringbuffer from having to know about capture_file type at all ↵Ulf Lamping1-2/+2
(decoupling dependencies) svn path=/trunk/; revision=13266
2004-12-28some code cleanup (comments changed)Ulf Lamping1-2/+2
svn path=/trunk/; revision=12848
2004-07-18Set the svn:eol-style property on all text files to "native", so thatGuy Harris1-1/+1
they have LF at the end of the line on UN*X and CR/LF on Windows; hopefully this means that if a CR/LF version is checked in on Windows, the CRs will be stripped so that they show up only when checked out on Windows, not on UN*X. svn path=/trunk/; revision=11400
2003-06-22Ringbuffer rework.Laurent Deniel1-3/+5
Almost completely rewritten in order to: - be able to use a unlimited number of ringbuffer files 0 specified with -b argument or in the GUI, means that the number of file is unlimited. else the maximum number of ring buffer files is arbitrarily set to 1024. - close the current file and open (truncating it) the next file at switch - set the final file name once open (or reopen) - avoid the deletion of files that could not be truncated (can't arise now) and do not erase empty files The idea behind that is to remove the limitation of the maximum # of ringbuffer files being less than the maximum # of open fd per process and to be able to reduce the amount of virtual memory usage (having only one file open at most) or the amount of file system usage (by truncating the files at switch and not the capture stop, and by closing them which makes possible their move or deletion after a switch). svn path=/trunk/; revision=7912
2002-08-28Removed trailing whitespaces from .h and .c files using theJörg Mayer1-7/+7
winapi_cleanup tool written by Patrik Stridvall for the wine project. svn path=/trunk/; revision=6117
2001-12-04Make the bytes-written information from Wiretap a long, as we allowGuy Harris1-0/+48
files to get that big. From Thomas Wittwer and Matthias Nyffenegger: Support for "ring buffer mode", wherein there's a ring buffer of N capture files; as each capture file reaches its maximum size (the ring buffer works only with a maximum capture file size specified), Ethereal rolls over to the next capture file in the ring buffer, replacing whatever packets might be in it with new packets. svn path=/trunk/; revision=4324