2013-11-29 11:21:39.6275 [PID=11032] [HOST#9649] Sending [RESULT#1212496 LATeah0069U_48.0_500_-4.01e-10_1] (est. dur. 1601.52s (0h26m41s52)) (max time 31151.75s (8h39m11s74))
2013-11-29 11:21:39.6300 [PID=11032] [locality] send_old_work(LATeah0069U_48.0_500_-4.01e-10_1) sent result created 347.4 hours ago [RESULT#1212496]
2013-11-29 11:21:39.6300 [PID=11032] [locality] Note: sent NON-LOCALITY result LATeah0069U_48.0_500_-4.01e-10_1
2013-11-29 11:21:39.6300 [PID=11032] [locality] send_new_file_work(): try to send old work
I think the reason that you get tasks from the Gamma Ray search is that the scheduler is resending lost work, that is work that's been allocated but for some reason is not present on your machine. Task selection via prefs don't apply when resending work so you'll keep getting them until there are no more missing tasks, but you should not get any new ones.
I checked host #9649 (the posted log is from a scheduler contact from this host) and there are no in progress Gamma Ray tasks so that host should not get any more of them unless you opt into that search again.
RE: 2013-11-29
)
I think the reason that you get tasks from the Gamma Ray search is that the scheduler is resending lost work, that is work that's been allocated but for some reason is not present on your machine. Task selection via prefs don't apply when resending work so you'll keep getting them until there are no more missing tasks, but you should not get any new ones.
I checked host #9649 (the posted log is from a scheduler contact from this host) and there are no in progress Gamma Ray tasks so that host should not get any more of them unless you opt into that search again.