* Ralf Hildebrandt <[EMAIL PROTECTED]>: > # /usr/local/scripts/tcpping 10.48.5.21 1521 > seq 0: tcp response from 10.48.5.21 [open] 0.459 ms > seq 1: tcp response from 10.48.5.21 [open] 0.515 ms > seq 2: tcp response from 10.48.5.21 [open] 0.468 ms > seq 3: tcp response from 10.48.5.21 [open] 0.467 ms > > but still no data in smokeping :(
smokeping invokes tcpping as: /usr/local/scripts/tcpping -C -x 10 10.48.5.21 1521 Which gives me: 10.48.5.21 : - - - - - - - - - - /usr/local/scripts/tcpping -x 10 10.48.5.21 1521 OTOH gives me: seq 0: tcp response from 10.48.5.21 [open] 0.543 ms seq 1: tcp response from 10.48.5.21 [open] 0.766 ms seq 2: tcp response from 10.48.5.21 [open] 0.632 ms seq 3: tcp response from 10.48.5.21 [open] 0.455 ms seq 4: tcp response from 10.48.5.21 [open] 0.672 ms seq 5: tcp response from 10.48.5.21 [open] 0.686 ms seq 6: tcp response from 10.48.5.21 [open] 0.621 ms seq 7: tcp response from 10.48.5.21 [open] 0.579 ms seq 8: tcp response from 10.48.5.21 [open] 0.581 ms ... Where "0.543 ms" which differs considerably from "-" in the former output. ARRRRGH. -C print in the same format as fping's -C option I found the bug. tcpping invokes tcptraceoute and the output format differs, depending on whether you use an IP or a HOSTNAME as argument. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to [EMAIL PROTECTED] _______________________________________________ smokeping-users mailing list smokeping-users@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
