Your message dated Fri, 5 Dec 2008 20:05:57 GMT
with message-id <[EMAIL PROTECTED]>
and subject line tkping has been removed from Debian, closing #398551
has caused the Debian Bug report #398551,
regarding TkPing: Configuration and logging problems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
398551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398551
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: tkping
Version:1.1.1-2

The system is a Compaq Deskpro EN, 1GHz CPU, 20GB HDD running Debian Testing
Etch

Configuration problem:
--------------------------------
I have problems configure the application thru the config files
/etc/tkping/tkping.conf and ~/.tkpingrc

I try to sett ping time to 5 sec and 1 packet at the time but I always get
the default values. It doesn't matter if I use the global conf-file
tkping.conf or the local one .tkpingrc.
Host configuration thru .tkpingrc works though.

******** START .tkpingrc ******
WinTitle:   Bewator2010
Packets:   1
Sleep:       5
LogFile:    /home/uffe/tkping/tkping.log

<message> Servrar
xxx.xxx.xxx.xxx  Norra
<blank>
<blank>
<blank>
xxx.xxx.xxx.xxx Mellersta
<blank>
xxx.xxx.xxx.xxx Soedra
xxx.xxx.xxx.xxx Vaestra
xxx.xxx.xxx.xxx Oesttra
<nextcolumn>

<message> Default GW
xxx.xxx.xxx.xxx Vns_router
xxx.xxx.xxx.xxx Ptaa_router
xxx.xxx.xxx.xxx Le_router
<blank>
nextcolumn>

<message> Lokalsystem
xxx.xxx.xxx.xxx Vaennaes
xxx.xxx.xxx.xxx Piteaa
xxx.xxx.xxx.xxx Luleaa_stn
xxx.xxx.xxx.xxx Luleaa_bg
********* END .tkpingrc *********

Beside the working host configuration, the only way for me to set anything
but default, is by the command line.

prompt:~$tkping -s 5 -p 1  -v  -w Bewator2010 -l
/home/uffe/tkping/tkping.log

And yet, WinTitle is not set and the log-file don't end up where I
specified, instead it ends up here ~/tkping.log

Logging problems:
--------------------------
The description of the logging parameter says "Log host-outages, periodic
stats, and errors to {fspec}."
The only log entries I get are the starts and stops of the application.

******** START tkping.log ********
tkping: 14Nov06-08:12:21 Running...
tkping: 14Nov06-08:12:21   by uffe as: tkping
tkping: 14Nov06-08:12:34 Complete.

tkping: 14Nov06-08:12:38 Running...
tkping: 14Nov06-08:12:38   by uffe as: tkping -s 5 -p 1 -v -w Bewator2010 -l
/home/uffe/tkping/tkping.log
tkping: 14Nov06-11:32:19 Complete.

tkping: 14Nov06-11:32:34 Running...
tkping: 14Nov06-11:32:34   by uffe as: tkping -s 5 -p 1 -v -w Bewator2010 -l
/home/uffe/tkping/tkping.log
********* END tkping.log *********

I haven't found any way to provoke a log entry of lost packets or lost
connection beside the starts and stops.
The only time I got anything else in the log file was when I used non
english caracters in the name of  one of the nodes and then clicked "down".
That rendered an errorr of "unknown name" or something. Sorry I didn't save
that, but I don't think it's relevant for the existing problems.

I really like the application. It is fullfills my monitoring needs right
now, but I do need the logging to work properly.

Best regards
Uffe Norberg

--- End Message ---
--- Begin Message ---
Version: 1.1.1-2+rm

The tkping package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/507811 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

--
Marco Rodrigues
http://Marco.Tondela.org


--- End Message ---

Reply via email to