Andrew Suffield 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?
Not all distributions include a tiny /etc/services (like Debian does). gateway:~ # wc -l /etc/services 14705 /etc/services gateway:~ # time shorewall restart Compiling... Shorewall configuration compiled to /root/shorewall/.restart Restarting Shorewall.... done. real 0m1.131s user 0m0.404s sys 0m0.304s gateway:~ # # time /usr/share/shorewall-perl/buildports.pl > /dev/null real 0m0.412s user 0m0.368s sys 0m0.040s gateway:~ # -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- 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
