Surveill@Home

[DrBob]

Did create account alrigth...Just waiting for them to fix the Ati-host issue...

The ATI host problem was corrected yesterday.

[Beerdrinker]

The ATI host problem was corrected yesterday.

Alrigth then!...I am attaching now....Will see if it works..


EDIT: It did work!!! I got 2 WU´s rigth away - and I am now doing work for SETI.USA....!

[c303a]

Not a lot of credit, but I notice that I am getting what seems like a lot of work according to the web site. Almost 200 wu's so far.

[zombie67]

I have noticed two problems running this project, and I am looking for confirmation from teammates.

1) It seems to hammer the network to the point where the "can't connect to the network" pop-up happens frequently. This has been confirmed by others on the project forum.

2) On my windows machines (but not my macs), something keeps killing the boinc client. The manager is still running, but can't connect to the localhost. CPU usage is zero. Check the processes, and the BOINC client is not running. It happens about once a day across all my windows machines. This started when I started running this project. So I have suspended this project on all my windows machines.

Since suspending, both 1 and 2 have stopped.

Is anyone else seeing #2?

[Cruncher Pete]

I have noticed two problems running this project, and I am looking for confirmation from teammates.

1) It seems to hammer the network to the point where the "can't connect to the network" pop-up happens frequently. This has been confirmed by others on the project forum.

2) On my windows machines (but not my macs), something keeps killing the boinc client. The manager is still running, but can't connect to the localhost. CPU usage is zero. Check the processes, and the BOINC client is not running. It happens about once a day across all my windows machines. This started when I started running this project. So I have suspended this project on all my windows machines.

Since suspending, both 1 and 2 have stopped.

Is anyone else seeing #2?

Yeh, I can confirm that. When I could not connect, I checked Task Manager and it was the project's WU that was taking all my 8Gb of RAM or close to it. The strange part is that it does not happen on all of my machines yet they are identical in build.

[zombie67]

Yeh, I can confirm that. When I could not connect, I checked Task Manager and it was the project's WU that was taking all my 8Gb of RAM or close to it. The strange part is that it does not happen on all of my machines yet they are identical in build.

Thanks. Could you please follow up to my post on their forum? I would like them to know it's not just me.

[DrBob]

I have noticed two problems running this project, and I am looking for confirmation from teammates.

1) It seems to hammer the network to the point where the "can't connect to the network" pop-up happens frequently. This has been confirmed by others on the project forum.

2) On my windows machines (but not my macs), something keeps killing the boinc client. The manager is still running, but can't connect to the localhost. CPU usage is zero. Check the processes, and the BOINC client is not running. It happens about once a day across all my windows machines. This started when I started running this project. So I have suspended this project on all my windows machines.

Since suspending, both 1 and 2 have stopped.

Is anyone else seeing #2?

Haven't noticed either problem with Surveill but will keep a closer eye on my machines and try to confirm.
I have noticed your #2 problem on one of my Win32 boxes, the culprit turned out to be FreeHal, since suspending FreeHall on that machine the problem has not re-occurred.

[zombie67]

Haven't noticed either problem with Surveill but will keep a closer eye on my machines and try to confirm.
I have noticed your #2 problem on one of my Win32 boxes, the culprit turned out to be FreeHal, since suspending FreeHall on that machine the problem has not re-occurred.

Hmm. I am running Freehal too, but that is not causing me any problems. It happens only when I turn on surveill.

[denim]

I still have not been able to attach.

[Fire$torm]

Haven't noticed either problem with Surveill but will keep a closer eye on my machines and try to confirm.
I have noticed your #2 problem on one of my Win32 boxes, the culprit turned out to be FreeHal, since suspending FreeHall on that machine the problem has not re-occurred.

Thanks. Could you please follow up to my post on their forum? I would like them to know it's not just me.

Hmm. I am running Freehal too, but that is not causing me any problems. It happens only when I turn on surveill.

Maybe it is related to BM version?