I run seti and cpdn on a linux box. If I start boinc with ./boinc and logout and it is a cpdn WU that is running then boinc and all children die. If I start boinc and its a seti WU to run then I can logout and the boinc process survives....and switches happily with seti and so forth no probs. Anyone else seen this. Boinc 4.32 btw. Cheers.

Yes, I have seen it. But I have no solution except:
1.run boinc as a service, so you can log in and log out
2.Never log out :o) (that's my solution: my box run 24/7)

> Yes, I have seen it. But I have no solution except:
> 1.run boinc as a service, so you can log in and log out
> 2.Never log out :o) (that's my solution: my box run 24/7)
>

Hmmm a service is a good idea. Thanks!
Regards
Ian

Try running it with "nohup" on linux

nohup ./boinc &

(puts in the background and ignores the hangup/logout signal. output messages from boinc wind up in nohup.out)

you can do this from the rc apropriate rc file too

cd /myboincdirectory
nohup ./boinc &