Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Rick on April 07, 2001, 12:23:19 PM

Title: SETI
Post by: Rick on April 07, 2001, 12:23:19 PM

Has someone got a Seti client up and running on a e-smith box?

Title: Re: SETI
Post by: Rob Hillis on April 07, 2001, 12:33:25 PM

Yep... SETI's running fine here... I haven't figured out how to completely integrate it into the template, but it's more or less fine... just doesn't get backed up...

Pop the Linux client in it's own directory (I'm using /usr/SETI) and create a file called 10SETI (or similar) in /etc/e-smith/templates/etc/crontab with the following contents...

---cut---
# cron entries to keep SETI@Home running...

00 * * * * root %cd /usr/SETI%./setiathome >/dev/null&
15 * * * * root %cd /usr/SETI%./setiathome >/dev/null&
30 * * * * root %cd /usr/SETI%./setiathome >/dev/null&
45 * * * * root %cd /usr/SETI%./setiathome >/dev/null&
---cut---

Once that's created, just type '/sbin/e-smith/signal-event console-save' at the command line to update all your config files, and everything should start running...

This runs the SETI client every 15 minutes to make sure it keeps running, even after it's completed a WU and sent it back.

Title: Re: SETI
Post by: Rick on April 09, 2001, 01:16:17 PM

Tnx. I did what you wrote above. I works perfect.

Title: Re: SETI
Post by: Rick on April 09, 2001, 07:59:40 PM

After all, it was not such a good idea. On my system PHP could not connect to MySQL anymore when I implemented the changes as mentioned above. Is this a bug or is the syntaxt above wrong?

This was the problem when opening Webmail f.e.

Call to undefined function: mysql_pconnect()

Title: Re: SETI
Post by: Rob Hillis on April 10, 2001, 03:30:43 PM

Rick wrote:

> After all, it was not such a good idea. On my system PHP
> could not connect to MySQL anymore when I implemented the
> changes as mentioned above. Is this a bug or is the syntaxt
> above wrong?

The addition to the cron file should not, AFAIK, affect MySQL... MySQL still works fine here.  SETI@Home does not use MySQL, nor does it use cron, so I can't see a reason for MySQL falling over...

Title: Re: SETI
Post by: Rick on April 10, 2001, 11:48:51 PM

I occurred after I did the console-save

After I got back to the old situation (without the CRON entry) the problem disappeared.

Title: Re: SETI
Post by: Rob Hillis on April 11, 2001, 05:27:16 AM

Rick wrote:

> I occurred after I did the console-save
> After I got back to the old situation (without the CRON
> entry) the problem disappeared.

Then I'm afraid I have no idea... like I said, things are working fine here, e-smith is quite happily churning through the work units, and the webmail application is not affected.

Perhaps someone else can shed some light?