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