View Single Post
  #5  
Old 9th May 2009, 00:21
glohmann glohmann is offline
Junior Member
 
Join Date: May 2009
Posts: 7
Thanks: 0
Thanked 1 Time in 1 Post
Default

pros:
- you not flood you log file with million of lines like:
May 8 22:55:01 neptun imapd: Connection, ip=[::ffff:127.0.0.1]
May 8 22:55:01 neptun imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
May 8 23:00:02 neptun pop3d: Connection, ip=[::ffff:127.0.0.1]
May 8 23:00:02 neptun pop3d: Disconnected, ip=[::ffff:127.0.0.1]
- You can be sure your daemon is running even if he serve a different port
- it is fast (e.g. no need to wait for timeouts)
- you can use it even for daemons not serving on a ip/port (e.g. amavisd)

cons:
- you may see a specific daemon running but still not know if one can connect
- some daemons serve several protocols (pop3, po3-ssl, ...) but you only know if the daemon itself is up

well ... maybe we could add both ... having the default 5 min polling just if the daemon itself is running ... and in the monitor GUI an additional button to check if specific services could be connected or not ... and if it fails then directly return a meaningfull error message if possible.
Reply With Quote