[OLSR-users] Fatal!scheduler could not get new_times.

[Andreas Tønnesen]

Hi Benny,

hmmm... actually times(2) is only considered to fail if it returns -1, 
so I guess I have made a mistake checking for a negative value. Try the 
attatched patch.

- Andreas

Benjamin Hagemann wrote:
> * Benny Hagemann <(spam-protected)> [051028 19:15]:
> 
>>can somebody tell me more about this error:
>>
>>---------- LIBRARY LOADED ----------
>>
>>Main address: 10.253.16.17
>>
>>Scheduler started - polling every 0.50 seconds
>>Max jitter is 1.250000
>>
>>Fatal!scheduler could not get new_times.
>>Invalid argument
>>OLSR EXIT: scheduler
>>Received signal 15 - shutting down
> 
> 
> here some strace output:
> 
> write(1, "Scheduler started - polling ever"..., 47Scheduler started - polling every 0.50 seconds
> ) = 47
> times({tms_utime=0, tms_stime=0, tms_cutime=0, tms_cstime=0}) =
> -2146400741
> times({tms_utime=0, tms_stime=0, tms_cutime=0, tms_cstime=0}) =
> -2146400741
> write(2, "Fatal!scheduler could not get ne"..., 58Fatal!scheduler could not get new_times.
> Invalid argument
> ) = 58
> time([1130520119])                      = 1130520119
> stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
> stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
> stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=837, ...}) = 0
> send(4, "<27>Oct 28 19:21:59 olsrd[14475]"..., 92, MSG_NOSIGNAL) = 92
> write(1, "OLSR EXIT: scheduler\n", 21OLSR EXIT: scheduler
> )  = 21
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users

-- 
Andreas Tønnesen
http://www.olsr.org
http://www.tønnesen.org
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: olsrd-times.patch
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20051028/33485ef3/attachment.ksh>