ipac-ng:

Version 1.09
	See CHANGES for details..


Version 1.05
	Config file syntax is now same as ipac version 1.90 and older.
	
Version 1.0

	As of this version, format of config file has changed. Take a look
	for it in ./contrib/sample_configs/kaiser.ipac.conf. Basically it's
	the same as an old one but you can not specify more that one port 
	(source\destination) in one line now. Surely you are still able to
	specify both of source and destination port but only one source and 
	one destination in a line. Maybe this will be fixed (does someone
	need this?). You _have_ to fill every field in config.

ipac:
Version 1.90

A major rewrite of ipac has been done and there are some points you 
should consider:

 o  The build process is now "autoconf" based. This means that there
    is no build "config" file to edit anymore. All settings are
    automatically determined by a script called "configure" - some of
    them can be changed manually, though.

 o  ipac now supports so-called "storage method backends". A storage
    method is a way to store the accounting data in a database. A
    default storage method is choosen at build time and compiled into 
    ipac. Still, a different storage method can be set on the command
    line of fetchipac and ipacsum at any time.
    
    The old method of storing the accounting data, one file per
    "fetch" in the data direcory, has now got a name: "plain-file". A
    plain-file storage can still be used without restriction. In fact,
    if you don't care about it, when the build process finds
    "plain-file" accounting data on the machine, it will set this as
    the default and everything is fine.   You can check which default
    storage method is compiled in: At build time, when running
    configure, watch out for a line saying

    	checking for default storage method... plain-file (data exists on this machine)

    At run time, call fetchipac with the '--help' option - it will
    tell you which default storage method is compiled in.

 o  If you don't have any plain-file style accounting data on the
    machine or if the build process does not find it, "gdbm" will be
    the default storage method. gdbm is the new storage method and
    it has several advantages: It does not waste disk space as
    plain-file and access to the data is much faster, especially with
    large databases.

 o  If you want to manually set the default storage method at build
    time, use the '--enable-default-storage=STORAGE_METHOD' option of
    configure. Replace STORAGE_METHOD with the name of the storage
    method you want to have as the default.

 o  If you have old plain-file style data and want to use the gdbm or
    any other (provided by a third party) storage method and want to
    convert your data, use the ipac-convert program. See the manual
    page for details.

 o  Similar to how the default storage method is found, configure
    chooses the directory for the accounting data. If there is a
    directory "/var/log/ip-acct", it is used (this used to be the
    default in ipac before 1.90). Otherwise, "/var/lib/ipac" is used
    which is much more linux filesystem standard compatible and makes
    more sense (ipac data is not log files but an application specific
    database).

    You can manually set the default data diretroy to use by setting
    the environment variable ipac_datadir before running configure. In
    any case, the directory can be set at run time.

 o  All ipac programs are now installed into /usr/local/sbin instead
    of /usr/local/bin. THIS MEANS YOU MIGHT HAVE TO REMOVE THE
    PROGRMAS FROM THE OLD PATHS so the new ones are found and executed
    indeed! (This change might cause a lot of confusion, but I wanted
    to have things The Right And Clean Way for the new major release.)

    
Version 1.03

If you use ipchains (kernel 2.1.* or 2.2.*) and you have a packet filter
firewall, read the ipacset man page, section BUGS. Firewall setup scripts
may interfere which ipac.


Version 0.99

If you update from a version before 0.99 and want to use the new gif image
creation functionality, you will need the perl GD library. ipacsum will
complain if you try to create images without it. Look for GD at
http://www.cpan.org/CPAN.html.


Version 0.98
If you update from versions before 0.98, you should check your scripts
for the way options to ipacsum are given. Because of the introduction of
long options names such as '--starttime' (same as -s), there must now be
a space character between the option character and its value. For example,
'ipacsum -s1998' worked before, but is incorrect now. You need to say
'ipacsum -s 1998'.

The above is not true and you can forget it again if you have a version of
the Getopt::Long package 2.10 or above.

$Id: UPDATE,v 1.5.2.1 2000/07/12 22:53:52 moritz Exp $
