On Wed, 21 Jul 2004 10:29:32 -0500 (CDT) "Joseph Booker" wrote: > I think what he was saying, is that einfo (and i guess ewarn also) > would be redirected to a file, what about the same file as the regular > PORT_LOGDIR, but with *.einfos.log files also? (or instead of?) Look, that's sample output from portlog-info: === 2004-07-08 12:56 === iptables-1.2.11-r2 === = /var/log/emerge/4528-iptables-1.2.11-r2.log = ... * This package now includes an initscript which loads and saves * rules stored in /var/lib/iptables/rules-save * This location can be changed in /etc/conf.d/iptables * * If you are using the iptables initsscript you should save your * rules using the new iptables version before rebooting. * * If you are uprading to a >=2.4.21 kernel you may need to rebuild * iptables. * * !!! ipforwarding is now not a part of the iptables initscripts. * Until a more permanent solution is implemented adding the following * to /etc/conf.d/local.start will enable ipforwarding at bootup: * echo "1" > /proc/sys/net/ipv4/conf/all/forwarding As you can see these *ARE* the einfo lines, so there's no need for other files like iptables.einfo.log, because the information is already there. Or maybe I'm just not getting what you're trying to tell me, which is always a possibility with me... ;-) Regards, Michael -- www.cargal.org GnuPG-key-ID: 0x90CA09E3 Jabber-ID: citizen428 [at] cargal [dot] org Registered Linux User #278726