[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [PATCH 2/2 master] Copy ifcfg.log into traceback and installed system.



On 08/23/2010 09:17 PM, Chris Lumens wrote:
diff --git a/pyanaconda/packages.py b/pyanaconda/packages.py
index 7d88d06..079dd67 100644
--- a/pyanaconda/packages.py
+++ b/pyanaconda/packages.py
@@ -72,6 +72,7 @@ def copyAnacondaLogs(anaconda):
                         ("/tmp/X.log", "anaconda.xlog"),
                         ("/tmp/program.log", "anaconda.program.log"),
                         ("/tmp/storage.log", "anaconda.storage.log"),
+                       ("/tmp/ifcfg.log", "anaconda.ifcfg.log"),
                         ("/tmp/yum.log", "anaconda.yum.log")):
          if os.access(fn, os.R_OK):
              try:
Do we really need this log on the filesystem post-installation?


Yes, it's easier to just ask for logs from installed system
then to ask to reproduce - there are cases when something
going wrong with networking doesn't prevent finishing
install (like no networking after boot, wrong configuration
of net devices not used for installing, esp. with kickstart).
It's based on my experience with bug reports I met. And
there is no cost except for /var/log being cluttered
with our logs - there you are right.

Also, it might be worth considering making /var/log/anaconda/ and
putting all this stuff in there.  We're starting to make a bigger and
bigger mess in /var/log.

I agree, I'll talk with Ales about it.


Radek


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]