[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

new portslave release 2001-07-09



This version will be uploaded to Unstable in a few days if there are no 
bugs reported.  Please test it out and let me know how it goes.


Russell Coker

----------  Forwarded Message  ----------

Subject: new release 2001-07-09
Date: Mon, 9 Jul 2001 18:11:33 +0200
From: Russell Coker <russell@coker.com.au>
To: portslave@linuxrouter.org

This version has more changes than most versions and should be treated
with extra caution, but it's passed all my tests and my most important
machine is connecting through it so I think it's good.

The config code now only keeps data in memory for the active line.
Previously we had an array of 512 entries for the maximum number of
lines, and the "all.*" entries were copies to all of them, which meant
many duplicated strings!  Now there's only one copy of the line
configuration data.

Doing this saves memory and allows increasing the maximum number of lines
without further cost (which is why I increased it to 1024 lines).  Now
the only code for which the maximum number of lines matters is
ctlportslave.  This saves about 500K of memory per copy of portslave, and
also may reduce the amount of calculation performed for reading the
config files.  This will really help for machines with small amounts of
RAM!!!

This is a major and significant change to the way the configuration file
is parsed, but according to my tests it works fine (and it's the type of
thing that will work perfectly or stuff up completely - it hasn't stuffed
up).

The other major change is to make pppd store the packet counts where we
can get them for RADIUS accounting.  So now we log packets!

I have written and tested the appropriate patch for pppd 2.4.1.  I have
written the patch for pppd 2.4.0 but not tested it (I don't run that
version of pppd).  I will write the patch for any version of pppd for
which I am sent a copy of the pristine upstream source.

Also the pppd startup message required changing the operation of utmp.
It's a minor thing which could result in ctlportslave giving the wrong IP
address during the early stages of ppp initialisation (will be correct
once the RADIUS start packet has been sent).

It's at http://www.coker.com.au/portslave/ .  Please test this as I'm
getting close to fixing everything I want to fix in Portslave...

portslave (2001-07-09) unstable; urgency=low

  * Rewrote all the config code to only have the configuration for the
line in
    use in memory.  Saves about 500K of resident RAM for each running
copy of
    Portslave.

  * Removed some cruft from ctlportslave, cut the binary from 30K to 13K.

  * Changed the maximum number of lines to 1024 (was 512).  Could make it
    larger if necessary.

  * Made pppd display the correct "started by user" message when using
terminal
    authentication.

  * Fixed the logging code properly.

  * Added ppp packet counting (seriously hacking pppd).

--
http://www.coker.com.au/bonnie++/     Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/       Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/     My home page

-------------------------------------------------------

-- 
http://www.coker.com.au/bonnie++/     Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/       Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/     My home page



Reply to: