#1 5.07b client interval problem

[Antoine Megens]

I've compiled the new 5.07b client on zipslack 3.9
for use on a FREESCO router
(http://www.freesco.info)
FREESCO is using a 2.0.38 or 2.0.39 kernel (yeah, I
know...ancient).

The client compiles without problems, but when
executed, only the first report is transmitted (with
correct data AFAIK).

After the first report, the client just "sits" there,
doing nothing.

It seems like the timer isn't started correctly or
something. I've tried the debug version too, but
that didn't reveal much.

If you need more feedback/ reports just let me
know.

[Carsten Klapp]

Logged In: YES
user_id=369655

Hmm, I will have to look into this, I don't have a solution off of the top of my head.

I believe I had this identical problem on my ancient MkLinux for PowerMac, but I gave up on that and upgraded to Debian Potato then Woody without further problems. Certain versions of Solaris also had some porblems with the Sigsuspend setitimer (actually the opposite problem, it would not suspend execution at all!) but this should be fixed now.

I'll think about this and probably ask for more information about your system. Do any transmission subsequent attempts show up in the syslog? Or only the first one?

Thanks,
Carsten