Branch: refs/heads/master
Home: https://github.com/fabbione/kronosnet
Commit: e7822e14021b86ce05f45d67fd579b561e2bfe07
https://github.com/fabbione/kronosnet/commit/e7822e14021b86ce05f45d67fd579b…
Author: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Date: 2010-11-21 (Sun, 21 Nov 2010)
Changed paths:
M cfg.c
M cfg.h
M vty_cli_cmds.c
Log Message:
-----------
vty: remove concept of auto-listeners/manual listeners
switch to a much simpler baseport and port range concept.
for now, only baseport is implementend and needs extra checks implementation.
portrange will come soon enough.
Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Branch: refs/heads/master
Home: https://github.com/fabbione/kronosnet
Commit: 11a54d069bc0cae1656f040990dbbb9fb6ce1a07
https://github.com/fabbione/kronosnet/commit/11a54d069bc0cae1656f040990dbbb…
Author: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Date: 2010-11-21 (Sun, 21 Nov 2010)
Changed paths:
M ring.c
M ring.h
M tests/ping_test.c
Log Message:
-----------
ring: fix ping calculation for good
finally I have been able to reproduce the problem and it's related to
the "unknown" source in MONOTONIC clock. It can rollover making the signed
comparison useless. Force unsigned long long for the calculation that
fixes the issue.
Switching from:
Notice: timediff: -345483470 interval: 1000000
To:
Notice: timediff: 18446744073387515858 interval: 1000000
Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Branch: refs/heads/master
Home: https://github.com/fabbione/kronosnet
Commit: 63cb9913f319302fb4411f882c5a93481e81b7f2
https://github.com/fabbione/kronosnet/commit/63cb9913f319302fb4411f882c5a93…
Author: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Date: 2010-11-21 (Sun, 21 Nov 2010)
Changed paths:
M ring.c
M ring.h
M tests/ping_test.c
Log Message:
-----------
ring: use long long instead of suseconds_t
it appears (but not totally sure) that suseconds_t is not easily portable.
On sparc it was showing, at random, some different behaviour.
Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com>