rsdsl/libpcap.git - the LIBpcap interface to various kernel packet capture mechanism, precompiled for musl x64 and aarch64

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix spelling	Josh Soref	2023-06-25	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* amount * anymore * authentication * availability * bracket * captured * casted * communications * compliant * configurable * cumulate * deinitialize * descriptors * didn't * disassembler * disassociate * distributions * divvy * doing * entries * everything * explicitly * explosion * expression * extracting * failed * family * find * github * global * implementations * incorrectly * intel * interlocked * justifying * know * launched * libraries * malloced * mask * maximum * network * nonexistent * number * occurred * optimizer * overflow * overwrite lower * packet * packetfilter * packets * parse hosts * payload * phase * programmers * promiscuous * protocol * receiving * redefinition * sampling * savefile * schwartz * should * snapshot * something * specifies * straightforward * stream * subdir * support * surrogate * suse * system is * test with * than * those * unmaintained * valid * way * western * wireshark Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
*	Add support for running rpcapd from inetd and inetd-alikes.	Guy Harris	2018-04-01	1	-0/+56
	When run from inetd and programs that support inetd-style program launching (xinetd, launchd, systemd, ...), we don't do a connection-accept loop; we're handed the input side of the connection as the standard input and the output side of the connection as the standard output, and should dive right into the service loop. We extract the initial connection initialization and cleanup stuff from daemon_serviceloop() and put it into the code that calls the service loop, in rpcapd.c; it's different in the four cases where we start a service loop (accepted connection on UN*X, accepted connection on Windows, run from inetd, active mode), so that cleans up daemon_serviceloop() a bit. Supply a sample launchd plist; we could also supply examples of inetd and xinetd config file entries, and systemd units.