datafeed monitor: whsumm --lowgran gets run twice for datafeeds that use datafeed-monitor

the client-whsumm.sh command run by the event listener is not passed --highgran-daily, so it runs highgran and lowgran, and then the lowgran-whsumm.sh (whsumm.sh --lowgran-after-highgran) runs lowgran again.

To reproduce:

Start lowgran-whsumm.sh with an account ID that has a datafeed.

Use cases

1) lowgran has not been run yet for that account. Expected result: client-whsumm.sh is passed --highgran-daily flag

2) lowgran has already been run for that account (presumably by lowgran-whsumm.sh). Expected result: client-whsumm.sh is not passed --highgran-daily so highgran and and lowgran data can be summarized (lowgran needs to be run again so the lowgran aggregates can be updated)

Here's how you can check the timestamp to see if any are actually conflicting. In this particular example, it's within 50 seconds but don't conflict.

therouxj@xml-03:~$ grep Spark /tmp/2011-04-30/clientsumm-0500.sh_05.log | grep 'ggregates' | grep BlackSingle | less

2011-04-30 05:24:14.327 (3) [P1T2]: Starting Account #435 Spark - BlackSingles aggregates for Wed Mar 30 00:00:00 PDT 2011 to <Sat Apr 30 00:00:00 PDT 2011

2011-04-30 05:26:18.338 (3) [P1T2]: Finished Account #435 Spark - BlackSingles aggregates for Wed Mar 30 00:00:00 PDT 2011 to <Sat Apr 30 00:00:00 PDT 2011

therouxj@xml-06:~$ grep 'BlackSingles aggregate' /tmp/2011-04-30/lowgran-whsumm.sh_??.log

2011-04-30 05:27:09.383 (3) [P1T7]: Starting Account #435 Spark - BlackSingles aggregates for Fri Apr 29 00:00:00 PDT 2011 to <Sat Apr 30 00:00:00 PDT 2011

2011-04-30 05:27:16.662 (3) [P1T7]: Finished Account #435 Spark - BlackSingles aggregates for Fri Apr 29 00:00:00 PDT 2011 to <Sat Apr 30 00:00:00 PDT 2011