kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/net/flowscan/pkg-plist

32 lines
946 B
Text
Raw Normal View History

- bump portrevision because important features were added to port 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
2001-03-25 17:54:48 +02:00
etc/rc.d/cflowd-base.sh.sample
- additional important port changes - 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.
2001-03-25 15:23:36 +02:00
etc/rc.d/cflowd-flowscan.sh.sample
- completely new functionalities, so bumped port revision 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
2001-03-25 13:48:48 +02:00
var/db/flows/bin/flowscan
var/db/flows/bin/FlowScan.pm
var/db/flows/bin/CampusIO.pm
var/db/flows/bin/SubNetIO.pm
var/db/flows/bin/locker
var/db/flows/bin/add_ds.pl
var/db/flows/bin/add_txrx
var/db/flows/bin/event2vrule
var/db/flows/bin/ip2hostname
var/db/flows/bin/CampusIO.cf.sample
var/db/flows/bin/Napster_subnets.boulder.sample
var/db/flows/bin/SubNetIO.cf.sample
var/db/flows/bin/flowscan.cf.sample
var/db/flows/bin/local_nets.boulder.sample
var/db/flows/bin/our_subnets.boulder.sample
- bump portrevision because important features were added to port 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
2001-03-25 17:54:48 +02:00
var/db/flows/graphs/Makefile.sample
- completely new functionalities, so bumped port revision 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
2001-03-25 13:48:48 +02:00
share/doc/flowscan/README
share/doc/flowscan/README.html
share/doc/flowscan/INSTALL
share/doc/flowscan/INSTALL.html
share/doc/flowscan/TODO
share/doc/flowscan/crontab.sample
share/doc/flowscan/cflowd.sample
share/doc/flowscan/flowscan.sample
@dirrm var/db/flows/graphs
@dirrm var/db/flows/bin
@dirrm var/db/flows
@dirrm var/db
@dirrm share/doc/flowscan
Reference in a new issue Copy permalink