After starting raddebug using the "raddebug -t 0" command, raddebug exited immediately. A typo in the special case comparison has been fixed, and raddebug now runs for 11.5 days in this situation.
Description of problem:
raddebug tool from freeradius normally exists in 60 seconds, this can be overriden by -t cli option. Man page of radebug mentions that passing "-t 0" to raddebug will make it run forever.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure freeradius to accept commands via control-socket (see raddebug manpage)
2. Start radiusd service
3. Start raddebug -t 0
raddebug immediately exists
raddebug keeps running
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
I faced the same problem. It's a typo in /usr/sbin/raddebug
Here's a patch:
--- raddebug.orig 2013-03-29 10:45:10.615000000 +0100
+++ /usr/sbin/raddebug 2013-03-29 10:45:51.946000000 +0100
@@ -52,7 +52,7 @@
- [ "$timout" = "0" ] && timeout=1000000
+ [ "$timeout" = "0" ] && timeout=1000000
u) condition="(User-Name == $OPTARG)"
I made a pull request with this fix
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.