Was testing out this great tftp server after having problems with native RHEL tftp-hpa server. But had a question on why it always overwrites the log file specified on the command line each time it is started? Is there a reason it doesnt append instead which would allow you to preserve all existing log info thru multiple stops/starts/restarts/reboots?
While on the subject of logging was surprised to see that it logs the same exact "Communication Error" log message from 10 different places in the cpp file. Similarly that the same exact "Timeout Error" message was logged from 3 different places in the cpp file. Just making these messages unique somehow would allow someone to determine where in the code a particular error was returned from. And with the communication errors when they were due to an errno being set by a called routine, would be great to provide that number also.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The logging is fixed, but Communication Error (it rarely happens) has different errno in Windows and Unix, thats why the errno is not being exposed as it would confuse (we keep code and errors as near as possible for Unix and Windows). Timeout is not a system error but only happens when reply is not received after 3 attempts, so errno do not come into question.
Thanks
Achal Dhir
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Inspite of setting the Append param value to true, the jboss server.log file is getting truncated on every restart. Is there anything else I need to set ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Was testing out this great tftp server after having problems with native RHEL tftp-hpa server. But had a question on why it always overwrites the log file specified on the command line each time it is started? Is there a reason it doesnt append instead which would allow you to preserve all existing log info thru multiple stops/starts/restarts/reboots?
While on the subject of logging was surprised to see that it logs the same exact "Communication Error" log message from 10 different places in the cpp file. Similarly that the same exact "Timeout Error" message was logged from 3 different places in the cpp file. Just making these messages unique somehow would allow someone to determine where in the code a particular error was returned from. And with the communication errors when they were due to an errno being set by a called routine, would be great to provide that number also.
Hello,
The logging is fixed, but Communication Error (it rarely happens) has different errno in Windows and Unix, thats why the errno is not being exposed as it would confuse (we keep code and errors as near as possible for Unix and Windows). Timeout is not a system error but only happens when reply is not received after 3 attempts, so errno do not come into question.
Thanks
Achal Dhir
<log4j:configuration debug="false" xmlns:log4j="http://jakarta.apache.org/log4j/"></log4j:configuration>
<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender"></appender>
Inspite of setting the Append param value to true, the jboss server.log file is getting truncated on every restart. Is there anything else I need to set ?