Custom Query (981 matches)

Running under vista sp1 x86 , the CPU time, Progress and to completion fields in the Tasks tab are not being updated to reflect status of task.

This bug has been reported in Debian's BTS (​#479204):

boinc-client 5.10.45-2 fails to run for any significant period of time on my powerpc (mac mini) hardware. The version in debian stable works with no trouble (5.4.11-4). Here is a segment from the log file and a back trace using gdb.

log file segment:

SIGSEGV: segmentation violation
Stack trace (7 frames):
/usr/bin/boinc_client[0x100544a0]
[0x100344]
/usr/bin/boinc_client[0x1003e08c]
/usr/bin/boinc_client[0x10019f70]
/usr/bin/boinc_client[0x1004397c]
/lib/libc.so.6[0xf9f4720]
/lib/libc.so.6[0xf9f48e0]

gdb session:

 (gdb) run --check_all_logins --redirectio --dir /var/lib/boinc-client
 Starting program: /usr/bin/boinc_client --check_all_logins --redirectio --dir /var/lib/boinc-client
 [Thread debugging using libthread_db enabled]
 [New Thread 0x48026880 (LWP 19048)]

 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 0x48026880 (LWP 19048)]
 HOST_INFO::users_idle (this=<value optimized out>, check_all_logins=false, idle_time_to_run=<value optimized out>)
    at hostinfo_unix.C:774
774     hostinfo_unix.C: No such file or directory.
        in hostinfo_unix.C
 (gdb) bt
 #0  HOST_INFO::users_idle (this=<value optimized out>, check_all_logins=false, idle_time_to_run=<value optimized out>)
    at hostinfo_unix.C:774
 #1  0x10019f70 in CLIENT_STATE::poll_slow_events (this=0x10099878) at client_state.C:499
 #2  0x1004397c in boinc_main_loop () at main.C:471
 #3  0x0f9f4720 in ?? () from /lib/libc.so.6
 #4  0x0f9f48e0 in __libc_start_main () from /lib/libc.so.6
 #5  0x00000000 in ?? ()

The code from client/hostinfo_unix.C which causes the SIGSEGV is:

766: inline bool all_tty_idle(time_t t, char *device, char first_char, int num_tty) {
767:     struct stat sbuf;
768:     char *tty_index = device + strlen(device) - 1;
769:     *tty_index = first_char;
770:     for (int i = 0; i < num_tty; i++, (*tty_index)++) {
771:         if (stat(device, &sbuf)) {
772:             // error looking at device; don't try any more
773:             return true;
774:         } else if (sbuf.st_atime >= t) {
775:             return false;
776:         }
777:     }
778:     return true;
779: }

I have just rejoined SETI, but I find it very confuseing, and I am haveing trouble understanding your manual on how to set it up, and I am not sure if it is working or not. It can run all the time, just not when I'm on the computer.

I'm ready to delete it again, since I do not know how to set up the SETI progaram, and I dont have the time to learn it. I do not find your program user frindly, so there is a very good chance that I will stop running Bonic all together. This is the same reason I stoped last time, and am now finding it too confuseing once more. Please work on makeing your program, less time consumeing, and easier to install and use.

From,

Gary Nelson noslenil

From: SETI@home To: noslenfl Sent: Wednesday, April 30, 2008 2:55 PM Subject: Please rejoin SETI@home

Dear noslenfl:

We'd like to invite you to reconnect with SETI@home. Our records show that you've been with SETI@home since 01 November 2004, but it's been 372 days since you last returned a work unit. We want you back, and here's why:

These are exciting times for SETI@home. Last year we implemented a new SETI@home data recorder at the Arecibo radio telescope in Puerto Rico. This recorder is attached to a state-of-the-art multibeam receiver, so we can now measure signals from 7 positions on the sky at once, with greater sensitivity to weak signals compared to the data from the flat feed antenna we've used since 1999. We've greatly increased the sensitivity of our data analysis, and the likelihood that we'll find the first signs of extraterrestrial life. We're also close to releasing a second application, Astropulse, which will look for extremely short pulses of astronomical (and possibly intelligent) origin.

With these new developments comes an increase in required computing power, for which we depend on people like you. We hope you will consider signing back on with SETI@home, and help in this wonderful scientific venture.

If you experienced problems running SETI@home, please try any of the resources listed at: ​http://setiathome.berkeley.edu/sah_help.php including the new BOINC Online Help System which lets you talk live, over the Internet, with a help volunteer: http://boinc.berkeley.edu/help.php

We thank you for your involvement in SETI@home, and hope that you rejoin us in our search for signals from other worlds.

-- The SETI@home team

To not get any more email from SETI@home, please click here.

SETI@home - ​http://setiathome.berkeley.edu Space Sciences Laboratory / 7 Gauss Way University of California, Berkeley, CA 92740-7450