o Sort pkg-plist
o Whitespace problems in Makefile
o Use MASTER_SITE_SOURCEFORGE and MASTER_SITE_SUBDIR
PR: 28861
Submitted by: Patrick Li <pat@databits.net>
not based on the patch offered (I already had prepared diffs more than
one week ago, but had no time to perform the commit). I choose to use
my patches instead of those from the PR, since they seemed even more
correct ;-)
version numbered distfile.
2. Fix the configurator class name in the script.
3. Use INSTALL_DATA rather than CP to install the docs.
4. bump PORTREVISION again.
able to track the version numbers of those, but if they increment before
the configurator does, we can use PORTREVISION. We'll bump that now too,
of course. We can't add the modem utility because there isn't a distfile
available that has a version number in it. :-(
Netmask are contiguous bits, wildcard masks don't need to be.
The former is accurate for defining subnets and the latter is useful for
describing ranges for firewalls, route maps, or other such things.
example:
10.0.10.0 is nntp1.domain.com, 10.0.11.0 is nntp2.local.com
access-list 185 permit tcp any gt 1023 10.0.10.0 0.0.1.0 eq nntp
script for those who've installed a Java 2 VM. Life will be
exponentially better when we can count on 'javavm -jar foo.jar' just
doing The Right Thing(tm).
Submitted by: dozens of angry scientists
- install configuration files with .dist suffix so that users configuration
files are not deleted on package removal
- create ${PREFIX}/var/netsaint/rw directory needed for correct operation
of CGI script
- fix netsaint.log file permission problem
- depend on netsaint-plugins port
PR: 26328
Submitted by: maintainer
netsaint port depends on us and this creates a circular dependency.
Instead create the netsaint user/group ourselves (which is the only
reason for the netsaint dependency).
PR: 26327
Submitted by: maintainer
This module overloads hashes so that the key can be a subnet as in
NetAddr::IP. When looking values up, an interpretation will be made to
find the given key within the subnets specified in the hash.
Care must be taken, as only strings that can be parsed as an IP address
by NetAddr::IP can be used as keys for this hash.
This fixes some bugs and introduces many new interesting netmask and
netblock manipulating routines.
Fixes contributed to the author by the MAINTAINER and your's truly.
Submitted by: Anton Berezin <tobez@tobez.org> [MAINTAINER]
we need gmake here, added it to run dependencies
therefore updated PORTREVISION, otherwise you don't get
the png file...
- updated pkg-message. You need to configure SNMP on your cisco
or Juniper router
to make it more functional and userfriendly
- added cflowd's startup script to FILESDIR, add startup options to
it, that are only valid for the patched cflowd. So later we overwrite
the sample startup script of "stock" cflowd.
This is done this way, because cflowd also can be used without flowscan.
But *if* we use cflowd with flowscan, we have to manage things to work
with flowscan.
- install sample Makefile to graphs directory, so you can generate
graphs more easily as being described in the docu (see INSTALL)
- Added comments to pkg-message file, that this Makefile has to be
updated whenever you add or remove protocol types in
${PREFIX}/var/db/flows/bin/CampusIO.cf
- comment post-install section more..
- keep_me file could be removed, since we install the sample Makefile
now in the graphs subdir
- modify sample startup script
- run in background properly
- use variables for progs (grep, perl, kill, ...)
- style (use $var consistently, spaces after io redirection)
- install startup script as cflowd-flowscan.sh.sample
to get an order, cflowd ports startup script will be named
cflowd-base.sh.sample, so that cflowd will be started first.
this was overdue, since this complex port needs more docu,
explanation, preparation, etc ...
- installation directory moved
from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows
to match our typical /var filesystem layout, but since I want
to package this port, I don't want to write into /var/filesystem
its up to the user, to move the data around later if he has a large
/var and likes the data to reside there.
- create needed directories in ${PREFIX}/var/db/flows (bin and graphs)
use a .keep_me file, so that things are packaged properly
- install needed documentation
the INSTALL file is essential as well as the various example file.
NOPORTDOCS only covers unneeded files, which are not crucial for
installation
- the ${PREFIX}/var/db/flows/bin directory carries the sample files
for the flowscan script. Therefore those sample files reside there.
Other sample files like the crontab settings are up to the user, so
they reside in ${PREFIX}/share/doc/flowscan
- install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since
this is a port that needs thinking and handcrafting config files before
use...
- added a pkg-message file, that explains pre-requisites (cisco configuration)
and other post installation tasks as well as a BIG WARNING, that enabling
Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION
routers might affect the routers switching performance.
You should know IF you need to do it and if its o.k. IF you enable it.
- output pkg-message on port based installation as well since the warnings
are important.
- updated PLIST
delayed so that every service has a chance to come up properly
before the next one begins
Additionally provide graceful delayed shutdown of services by
using killall -15.
Install startup script as .sample file, since cflowd (and flowscan)
are not easy ports. You should read the docu properly.
