You can disregard this patch if you find it horrible.
I haven't thought about something that would fit better into
our logging system yet.
---
gui.py | 2 ++
network.py | 24 ++++++++++++++++++++++++
2 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/gui.py b/gui.py
index 307f5dc..6d7ecc9 100755
--- a/gui.py
+++ b/gui.py
@@ -976,7 +976,9 @@ class InstallInterface(InstallInterfaceBase):
if not just_setup:
self.anaconda.network.updateActiveDevices([install_device])
+ network.logIfcfgFiles(header="========== before nm-c-e run
")
runNMCE(self.anaconda)
+ network.logIfcfgFiles(header="========== after nm-c-e run
")
self.anaconda.network.update()
diff --git a/network.py b/network.py
index 9bbb935..a7c474e 100644
--- a/network.py
+++ b/network.py
@@ -238,6 +238,30 @@ def getActiveNetDevs():
ret.sort()
return ret
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-04-2010, 03:03 AM
David Cantrell
A bit lame ifcfg files logging (#520146)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not horrible, but I'm not crazy about the spurious log file output such as:
========== before nm-c-e run
Those entries can stay, but make them log at the DEBUG level.
On Tue, 27 Apr 2010, Radek Vykydal wrote:
You can disregard this patch if you find it horrible.
I haven't thought about something that would fit better into
our logging system yet.
---
gui.py | 2 ++
network.py | 24 ++++++++++++++++++++++++
2 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/gui.py b/gui.py
index 307f5dc..6d7ecc9 100755
--- a/gui.py
+++ b/gui.py
@@ -976,7 +976,9 @@ class InstallInterface(InstallInterfaceBase):
if not just_setup:
self.anaconda.network.updateActiveDevices([install_device])
+ network.logIfcfgFiles(header="========== before nm-c-e run
")
runNMCE(self.anaconda)
+ network.logIfcfgFiles(header="========== after nm-c-e run
")
self.anaconda.network.update()
diff --git a/network.py b/network.py
index 9bbb935..a7c474e 100644
--- a/network.py
+++ b/network.py
@@ -238,6 +238,30 @@ def getActiveNetDevs():
ret.sort()
return ret
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-05-2010, 01:04 PM
Radek Vykydal
A bit lame ifcfg files logging (#520146)
David Cantrell wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not horrible, but I'm not crazy about the spurious log file output
such as:
========== before nm-c-e run
Those entries can stay, but make them log at the DEBUG level.
It is logged into separate /tmp/ifcfg.log, so it doesn't polute
log files we have. Also I don't think it is using much resources,
and it can be pretty handy info that can be asked from bz reporter,
it is a source of information about what user set in nm-c-e,
so I'd not limit it to debug mode.
Radek
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-06-2010, 02:50 PM
David Cantrell
A bit lame ifcfg files logging (#520146)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 5 May 2010, Radek Vykydal wrote:
David Cantrell wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not horrible, but I'm not crazy about the spurious log file output such as:
========== before nm-c-e run
Those entries can stay, but make them log at the DEBUG level.
It is logged into separate /tmp/ifcfg.log, so it doesn't polute
log files we have. Also I don't think it is using much resources,
and it can be pretty handy info that can be asked from bz reporter,
it is a source of information about what user set in nm-c-e,
so I'd not limit it to debug mode.