[OneMacGuy]

I just decided to try and see if it maybe they changed something about the way they wrote the v.4 client that it might now work with our firewalls at work.

It Does Now!!!

I just added my Dual G5 and next comes the MDD Dual 867! I may even try and add a P4 or two to the mix for grins. I just hope that it can return WUs. The older version would not even get work.

If you had trouble getting it to run at work before, try it again now.

[OneMacGuy]

Originally posted by OneMacGuy:
I just decided to try and see if it maybe they changed something about the way they wrote the v.4 client that it might now work with our firewalls at work.

It Does Now!!!

Unfortunately, the client is unable to send results back to the server! The G5 Dually has a total of 6 WUs completed and no way to transmit.

Anyone know how long it will be able to continue without an upload?

Can I let it work several days and then copy the whole directory to a cd and carry it home and upload it?

[reader50]

The built-in queue will hold an absolute maximum of 10 work units. If the client can't upload and completes 10, it will dump the oldest unit and overwrite it with a new one to crunch.

If you floppy the data out, you may need the entire folder. Certainly client.cfg and queue.dat, possibly the others for security checking. Since the queue.dat file has had different formats across platforms, you will need the same client version to upload it at home.

[Scotttheking]

Try running it with the dump switch only.
It may dump.

[OneMacGuy]

Originally posted by Scotttheking:
Try running it with the dump switch only.
It may dump.

I tried the -send all switch, nada...

That means that 13 completed WUs are probably gonna go to waste. I have a 2.8 P4, an XP3200 and a Dual G5 all sitting here in my office that I cannot use. What a waste!!! I will try to take the work home on a CD and see if I can upload it from there.

[Turias]

Do you have computers somewhere else that are always connected and that run the same OSes you use?

If so, you could probably write a simple script that

1) tars/zips your entire F@H folder once every few days
2) sends the tar/zip to said machine outside your firewall with scp or ftp

The outside machine could then run a cron job that, at midnight every night, checks to see if the tar/zip has been uploaded. If it has, it runs the client, sends the results, and then deletes everything.

[Ravens]

Originally posted by Turias:
Do you have computers somewhere else that are always connected and that run the same OSes you use?

If so, you could probably write a simple script that

1) tars/zips your entire F@H folder once every few days
2) sends the tar/zip to said machine outside your firewall with scp or ftp

The outside machine could then run a cron job that, at midnight every night, checks to see if the tar/zip has been uploaded. If it has, it runs the client, sends the results, and then deletes everything.

Or Rsync through a SSH tunnel

[OneMacGuy]

Originally posted by Turias:
Do you have computers somewhere else that are always connected and that run the same OSes you use?

If so, you could probably write a simple script that

1) tars/zips your entire F@H folder once every few days
2) sends the tar/zip to said machine outside your firewall with scp or ftp

The outside machine could then run a cron job that, at midnight every night, checks to see if the tar/zip has been uploaded. If it has, it runs the client, sends the results, and then deletes everything.

I work at a secure government site, no way to do that. I may try to use a cdrw disk to tote the wu's home and upload them.