On 09/10/2007, Andrew Suffield <[EMAIL PROTECTED]> wrote:
> I find myself wondering why buildports.pl exists at all. Tom, did you
> have anything in particular in mind? I observe the following on my
> (admittedly pretty fast) desktop:
>
> [EMAIL PROTECTED]:~/src/shorewall-perl-4.0.3$ time perl buildports.pl
> >/dev/null
> real 0m0.084s
>
> Given that the relevant files can be loaded and parsed in under .1
> seconds (and I would not expect them to be difficult to parse, since
> libc does it all the time anyway, in each new process spawned), there
> does not appear to be a performance issue here that would prevent
> parsing services and protocols every time the shorewall compiler is
> invoked. Is there some other reason for doing it this way?
>
A previous announcement from Tom contained this:
"3) Previously, Shorewall-perl read /etc/protocols and /etc/services
during compiler startup to build internal protocol and service
tables. This had a fixed cost of up to one half second or more,
depending on the speed of the system and the distribution
(The /etc/services released with OpenSuSE 10.2 is over 14,000
lines!!) These tables are now initialized by the Perl compiler
which speeds up compilation considerably."
So, I am guessing that you (Andrew) are using a distribution with a
sane number of lines in /etc/services, rather than OpenSuSe :).
Jonathan.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
