Perhaps some additional info is warranted. The loghost in question is servicing messges from about 40 other machines. Some of the messges aren't being recorded properly(if at all). I assumed either a UDP issue or syslogd. A sniffer and netstat showed no UDP issues. So I am trying to determing how far I can push syslogd. | [reply] |
Ahhh ok in this case, forking off as many copies of your script as you can get away with to flood the syslog server with connections is the way to go, probably somewhere around 50-100 forked children is a good place to start, have the parent spawn off the children who each attempt one connection then die, that way the parent can launch another child and keep track of how many connection attempts where made and you can compare that to how many syslog entries exist. Be sure to run top in another terminal the first couple tests and make sure you arn't swaping out..if so reduce the number of children forked, if you have lots of memory free increase the number..
| [reply] |