pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2004-12-28	The default location of the pkgsrc-installed rc.d scripts is now	reed	1	-2/+2
	under share/examples/rc.d. The variable name already was named RCD_SCRIPTS_EXAMPLEDIR. This is from ideas from Greg Woods and others. Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism (as requested by wiz).
2004-04-23	mk/bsd.pkg.install.mk now automatically registers	reed	1	-2/+1
	the RCD_SCRIPTS rc.d script(s) to the PLIST. This GENERATE_PLIST idea is part of Greg A. Woods' PR #22954. This helps when the RC_SCRIPTS are installed to a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later, the default RCD_SCRIPTS_EXAMPLEDIR will be changed to be more clear that they are the examples.) These patches also remove the etc/rc.d/ scripts from PLISTs (of packages that use RCD_SCRIPTS). (This also removes now unused references from openssh* makefiles. Note that qmail package has not been changed yet.) I have been doing automatic PLIST registration for RC_SCRIPTS for over a year. Not all of these packages have been tested, but many have been tested and used. Somethings maybe to do: - a few packages still manually install the rc.d scripts to hard-coded etc/rc.d. These need to be fixed. - maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
2004-04-13	Cleaned up, use buildlink3	adam	1	-20/+6

2004-01-27	uppercase IP acronym, tabify.	grant	1	-5/+5

2004-01-24	replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.	grant	1	-2/+2

2003-12-23	Make this work with gcc3 (no more multi-line string constants).	agc	2	-1/+115

2003-09-19	Update HOMEPAGE and/or MASTER_SITES	dent	1	-2/+2

2003-07-30	Convert to use the bsd.pkg.install.mk framework:	jmmv	5	-22/+22
	- Install sample file in the examples directory. - Honour PKG_SYSCONFDIR properly. - Use RCD_SCRIPTS to handle the rc.d script. As a result, bump PKGREVISION to 2.
2003-05-06	Drop trailing whitespace. Ok'ed by wiz.	jmmv	1	-2/+2

2003-05-02	Dependency bumps, needed because of devel/pth's major bump, and related	wiz	1	-1/+2
	dependency bumps.
2003-04-06	Import iplog-2.2.3: Iplog is a tool using pcap to log ip traffic	hubertf	6	-0/+100
	iplog is a TCP/IP traffic logger. Currently, it is capable of logging TCP, UDP and ICMP traffic. Adding support for other protocols should be relatively easy. iplog's capabilities include the ability to detect TCP port scans, TCP null scans, FIN scans, UDP and ICMP "smurf" attacks, bogus TCP flags (used by scanners to detect the operating system in use), TCP SYN scans, TCP "Xmas" scans, ICMP ping floods, UDP scans, and IP fragment attacks. iplog is able to run in promiscuous mode and monitor traffic to all hosts on a network. iplog uses libpcap to read data from the network and can be ported to any system that supports pthreads and on which libpcap will function. Submitted by Martin Mersberger <gremlin@portal-to-web.de> in PR 20887