pcap_tstamp_type_name_to_val(3pcap) [osf1 man page]
PCAP_TSTAMP_TYPE_NAME_TO_VAL(3PCAP)PCAP_TSTAMP_TYPE_NAME_TO_VAL(3PCAP)NAME
pcap_tstamp_type_name_to_val - get the time stamp type value corresponding to a time stamp type name
SYNOPSIS
#include <pcap/pcap.h>
int pcap_tstamp_type_name_to_val(const char *name);
DESCRIPTION
pcap_tstamp_type_name_to_val() translates a time stamp type name to the corresponding time stamp type value. The translation is case-
insensitive.
RETURN VALUE
pcap_tstamp_type_name_to_val() returns 0 on success and PCAP_ERROR on failure.
SEE ALSO pcap(3PCAP), pcap_tstamp_type_val_to_name(3PCAP)
21 August 2010 PCAP_TSTAMP_TYPE_NAME_TO_VAL(3PCAP)
Check Out this Related Man Page
PCAP_SET_TSTAMP_TYPE(3PCAP)PCAP_SET_TSTAMP_TYPE(3PCAP)NAME
pcap_set_tstamp_type - set the time stamp type to be used by a capture device
SYNOPSIS
#include <pcap/pcap.h>
int pcap_set_tstamp_type(pcap_t *p, int tstamp_type);
DESCRIPTION
pcap_set_tstamp_type() sets the the type of time stamp desired for packets captured on the pcap descriptor to the type specified by
tstamp_type. It must be called on a pcap descriptor created by pcap_create() that has not yet been activated by pcap_activate().
pcap_list_tstamp_types() will give a list of the time stamp types supported by a given capture device. See pcap-tstamp(7) for a list of
all the time stamp types.
RETURN VALUE
pcap_set_tstamp_type() returns 0 on success if the specified time stamp type is expected to be supported by the capture device, PCAP_WARN-
ING_TSTAMP_TYPE_NOTSUP on success if the specified time stamp type is not supported by the capture device, PCAP_ERROR_ACTIVATED if called
on a capture handle that has been activated, and PCAP_ERROR_CANTSET_TSTAMP_TYPE if the capture device doesn't support setting the time
stamp type.
SEE ALSO pcap(3PCAP), pcap_list_tstamp_types(3PCAP), pcap_tstamp_type_name_to_val(3PCAP), pcap-tstamp(7)
21 August 2010 PCAP_SET_TSTAMP_TYPE(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)