-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marty E. Hillman wrote: >> There already is some effort going towards monitoring the agents' > status >> from the server. I don't know how feasible this would be (I'm not a >> developer). The traffic to the server is sent over UDP, so it's kind > of >> "send and forget". I don't know if there is really any two-way >> communications. If there is, this should be relatively trivial to >> implement. I'll add it to the bug as well. > - -- >> gentux > > UDP being connectionless, I don't see how the client can possibly "know" > that the message was received; however, a modifiable threshold on the > server could possibly help with the issue. For example, a setting in > the .conf file that tells it to expect 5 messages every 15 minutes, > otherwise send an alert (numbers complete subject to user > determination). Of course, a better place for the setting would be in > the clients.conf file so that you can set these specs per client rather > than an overall setting for the server.
Like I said, "send and forget". But it could be feasible to encode message acknowledgments into the body of the packet, which was the possible two-way reference. I haven't looked that deeply into the code to know for sure, plus since I don't really know C, it would be a bunch of guesswork. I actually suggested switching the connection to TCP, and monitoring state. That way the server would know if an agent died or if there was some problem in comms between the two. But, depending on the size of the environment, unforeseen performance issues might arise. - -- gentux echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge' gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239 D840 4CF0 39E2 18D3 4A9E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE72qJTPA54hjTSp4RAr2rAKC0mh1wAaSFLw1ComzUFWsZjNE3fgCcCsav YV85vgUmuS7cJtOq9X6I5G0= =ze+Z -----END PGP SIGNATURE-----
