This one time, at band camp, Alexander Clouter said:
> Hi,
>
> Finally got it with a GDB. I have a debugging symbols corefile if anyone is
> interested...or should I report this upstream.
You can submit it to this bug report, or upstream as you wish. I
suspect upstream is unlikely to be intere
Hi,
Finally got it with a GDB. I have a debugging symbols corefile if anyone is
interested...or should I report this upstream.
I am running 1.1.7-1.
Cheers
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Aug 09, 2007 at 06:08:27PM +0200, Alexandre LISSY said:
> From what I remember, I had the problem before, and solved it by copying the
> rlm_*.a.
>
> However, for the log output, I'm going to repackage, and save stderr&stdout
> so
> you can see them.
The only thing I can imagine is tha
On Thu, Aug 09, 2007 at 12:34:01PM +0200, Alexandre LISSY said:
> Any idea what's this supposed to do ?
>
> 176 dh_shlibdeps -a
> 177 for pkg in $(shell grep ^Package debian/control | awk '{print
> $$2}') ; do \
> 178 if dh_shlibdeps -p $$pkg -- -O | grep -q libssl; then
On Thu, Aug 09, 2007 at 12:15:46PM +0200, Alexandre LISSY said:
> Le jeudi 09 août 2007 12:06, vous avez écrit :
> > This one time, at band camp, Alexandre LISSY said:
> > > Hi,
> > >
> > > I'm also experiencing this issue, with freeradius 1.1.3 under Debian
> > > Etch. All I've noticed is that doi
This one time, at band camp, Alexandre LISSY said:
> Hi,
>
> I'm also experiencing this issue, with freeradius 1.1.3 under Debian Etch.
> All
> I've noticed is that doing a strace on the process shows up
> a "futex(0xdeadbeef, FUTEX_WAIT,2)", looking like some kind of deadlock.
>
> This is a F
Hi,
I'm also experiencing this issue, with freeradius 1.1.3 under Debian Etch. All
I've noticed is that doing a strace on the process shows up
a "futex(0xdeadbeef, FUTEX_WAIT,2)", looking like some kind of deadlock.
This is a FreeRADIUS 1.1.3-3 recompiled from debian's sources to add eap-tls
s
Hi,
I experienced this problem in woody and yesterday it reared it's ugly head in
etch. This was never a showstopper as we used to have two RADIUS servers and
I had beaten nagios to email me when one of them died.
However I am in the middle of redoing a huge chuck of the network
infrastructur
Hi Mark,
On Wed, Jul 04, 2007 at 02:56:57PM +0100, Mark Hymers wrote:
> On Thu, 19, Apr, 2007 at 09:06:44PM +0100, Mark Hymers spoke thus..
> > Can you please let us know whether this bug is reproducible in either
> > the etch version (1.1.3-3) or the current sid version (1.1.6-1).
>
> Could I ju
On Thu, 19, Apr, 2007 at 09:06:44PM +0100, Mark Hymers spoke thus..
> Can you please let us know whether this bug is reproducible in either
> the etch version (1.1.3-3) or the current sid version (1.1.6-1).
Hi,
Could I just remind you that we'd like to know whether this bug is
reproducible in eit
On Sat, 17, Mar, 2007 at 11:30:52AM +0100, Andre Beck spoke thus..
> Package: freeradius
> Version: 1.0.2-4sarge3
> Severity: important
Hi,
Can you please let us know whether this bug is reproducible in either
the etch version (1.1.3-3) or the current sid version (1.1.6-1).
Thanks,
Mark
--
Ma
This one time, at band camp, Andre Beck said:
> Hi,
>
> I'm running freeradius from Sarge in almost the default configuration,
> the only exception beeing GDBM mode for users file access. There are
> some hundred users in the file and two Cisco NAS query the server.
>
> Every now and then, typica
Package: freeradius
Version: 1.0.2-4sarge3
Severity: important
Hi,
I'm running freeradius from Sarge in almost the default configuration,
the only exception beeing GDBM mode for users file access. There are
some hundred users in the file and two Cisco NAS query the server.
Every now and then, ty
13 matches
Mail list logo
