PCAP_DUMP_FLUSH(3PCAP)PCAP_DUMP_FLUSH(3PCAP)NAME
pcap_dump_flush - flush to a savefile packets dumped
SYNOPSIS
#include <pcap/pcap.h>
int pcap_dump_flush(pcap_dumper_t *p);
DESCRIPTION
pcap_dump_flush() flushes the output buffer to the ``savefile,'' so that any packets written with pcap_dump() but not yet written to the
``savefile'' will be written.
RETURN VALUE
pcap_dump_flush() returns 0 on success and -1 on failure.
SEE ALSO pcap(3PCAP), pcap_dump_open(3PCAP), pcap_dump(3PCAP)
5 April 2008 PCAP_DUMP_FLUSH(3PCAP)
Check Out this Related Man Page
PCAP_DUMP_OPEN(3PCAP)PCAP_DUMP_OPEN(3PCAP)NAME
pcap_dump_open, pcap_dump_fopen - open a file to which to write packets
SYNOPSIS
#include <pcap/pcap.h>
pcap_dumper_t *pcap_dump_open(pcap_t *p, const char *fname);
pcap_dumper_t *pcap_dump_fopen(pcap_t *p, FILE *fp);
DESCRIPTION
pcap_dump_open() is called to open a ``savefile'' for writing. fname specifies the name of the file to open. The file will have the same
format as those used by tcpdump(1) and tcpslice(1). The name "-" in a synonym for stdout.
pcap_dump_fopen() is called to write data to an existing open stream fp. Note that on Windows, that stream should be opened in binary
mode.
p is a capture or ``savefile'' handle returned by an earlier call to pcap_create() and activated by an earlier call to pcap_activate(), or
returned by an earlier call to pcap_open_offline(), pcap_open_live(), or pcap_open_dead(). The link-layer type and snapshot length from p
are used as the link-layer type and snapshot length of the output file.
RETURN VALUES
A pointer to a pcap_dumper_t structure to use in subsequent pcap_dump() and pcap_dump_close() calls is returned on success. NULL is
returned on failure. If NULL is returned, pcap_geterr(p) can be used to get the error text.
SEE ALSO pcap(3PCAP), pcap_create(3PCAP), pcap_activate(3PCAP), pcap_open_offline(3PCAP), pcap_open_live(3PCAP), pcap_open_dead(3PCAP),
pcap_dump(3PCAP), pcap_dump_close(3PCAP), pcap_geterr(3PCAP), pcap-savefile(5)
5 April 2008 PCAP_DUMP_OPEN(3PCAP)
Hi Folks,
Today hasn't been the best one of my career in IT.
I've been a contractor for a major utility company for a number of years, on a number of seperate IT contracts mostly Unix. The company had 10 different flavours of unix and multiple different varsions of most of them.
At the... (3 Replies)