You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-cvs@jakarta.apache.org by ce...@apache.org on 2001/09/21 00:37:10 UTC

cvs commit: jakarta-log4j/src/docbook trouble.xml

ceki        01/09/20 15:37:10

  Modified:    src/docbook trouble.xml
  Log:
  
  
  Revision  Changes    Path
  1.2       +56 -2     jakarta-log4j/src/docbook/trouble.xml
  
  Index: trouble.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-log4j/src/docbook/trouble.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- trouble.xml	2001/09/20 22:19:07	1.1
  +++ trouble.xml	2001/09/20 22:37:10	1.2
  @@ -130,8 +130,10 @@
   
         <qandaentry>
   	<question>
  -	  <function>ClassCastException</function> when instantiating
  -	  <function>Logger</function> subclasses.
  +	  <para>
  +	    <function>ClassCastException</function> when instantiating
  +	    <function>Logger</function> subclasses.
  +	  </para>
   	</question>
   
   	<answer>
  @@ -176,9 +178,61 @@
   
         <qandaentry>
   	<question>
  +	  <para>log4j:WARN No such property [xyz] in
  +	  some appender or layout</para>
  +
   	</question>
   
   	<answer>
  +
  +	  <para>If during log4j configuration you get a warning about
  +	    an inexistent property, then you have probably misspelled
  +	    a property or entered a truly unrecognized property for
  +	    the component you are trying to configure in the
  +	    configuration file.
  +	  </para>
  +
  +	  <para>Log4j version 1.0 did not complain about unrecognized
  +	      properties whereas log4j version 1.1 and later do
  +	      complain.
  +	  </para>
  +	</answer>
  +      </qandaentry>
  +
  +      <qandaentry>
  +	<question>
  +	  <para>I cannot log to syslogd under linux.</para>
  +	</question>
  +
  +	<answer>
  +
  +	  <para>If you are trying to log to the Unix syslog under
  +	  Linux using the <ulink
  +	  url="../api/org/apache/log4j/net/SyslogAppender.html">SyslogAppender</ulink>,
  +	  then the Linux syslog daemon must be configured to accept
  +	  log input from the network.  Otherwise, you will get an
  +	  <function>IOException: connection refused</function>.
  +	  </para>
  +
  +	  <para>This can be done by adding the <function>-r</function> option when starting
  +	    the daemon. Or more precisely:</para>
  +
  +	  <orderedlist>
  +	    <listitem>
  +	      <para>Login as the <function>root</function> user</para>
  +	    </listitem>
  +	    
  +	    <listitem>
  +	      <para>Edit file <function>/etc/rc/init.d/syslog</function>
  +	      <programlisting>
  +  case "$1" in
  +  start)
  +        echo -n "Starting system logger: "
  +        daemon syslogd -r
  +	      </programlisting>
  +	      </para>
  +	    </listitem>
  +	  </orderedlist>
   	</answer>
         </qandaentry>
   	
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-cvs-help@jakarta.apache.org