Re: [xcat-user] xcatd logging/debugging

[Lissa V. <li...@us...>]

Well we do the same thing when needing to debug xcatd.  Although we just
usually comment out the two lines to see the information.  Only for debug
though.  It is a good thing while developing or if you have a problem.    I
would not recommend on a production system.

Lissa K. Valletta
2-3/T12
Poughkeepsie, NY 12601
(tie 293) 433-3102





From:	Arif Ali <ma...@ar...>
To:	"Mailing list, xCAT" <xca...@li...>
Date:	08/18/2011 12:08 PM
Subject:	[xcat-user] xcatd logging/debugging



Hi list,

I was wondering if this change is a good idea or not, as I tend to make
this change on most if not all of my installs so that i can get debugging
information, or is the consensus that if debugging is required then make
the relevant modifications for that purpose.

--- xcatd.orig 2011-08-18 17:00:02.000000000 +0100
+++ xcatd 2011-08-18 17:00:29.000000000 +0100
@@ -198,8 +198,8 @@
     xCAT::MsgUtils->message("S","Can't read /dev/null: $!");
     die;
   }
-  open STDOUT, '>/dev/null';
-  open STDERR, '>/dev/null';
+  open STDOUT, '>> /var/log/xcat.log';
+  open STDERR, '>> /var/log/xcat.log';
   $0='xcatd';
   $progname = \$0;
   if (! setsid) {

--
Arif Ali

catch me on freenode IRC, username: arif-ali
------------------------------------------------------------------------------

Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
xCAT-user mailing list
xCA...@li...
https://lists.sourceforge.net/lists/listinfo/xcat-user