ree...@gmail.com wrote:
This behavior not seen when logging to files or syslog, only when set to
stdout/stderr. So, my best guess after looking the source is that logging to
stdout/err does not go to same processing flow as the others.
I have searching for this issue but still no luck, do
On Tue, May 25, 2010 at 1:06 PM, Alan DeKok al...@deployingradius.com wrote:
ree...@gmail.com wrote:
This behavior not seen when logging to files or syslog, only when set to
stdout/stderr. So, my best guess after looking the source is that logging to
stdout/err does not go to same processing
Dear Users,
We are in the process migrating our production server running 2.1.3 version and
testing the pre 2.1.9. All running well so far except the logging output
generated by radiusd.
We set logging to stderr or stdout, when started with debug_level = 0, no log
generated except the first
3 matches
Mail list logo
