I own a "managed server" at Germany biggest server hoster (1und1).

Different to a "root" server you cannot configure the OS (Suse Linux), no Kernel compilation, no packet installation etc.

I can access the server with SSH, and I start the client. But the task will be killed with "Signal 15":
***
p35394547:/kunden/homepages/14/d38373691/htdocs/seti > ./boinc318
2004-06-25 13:19:47 [---] Starting BOINC client version 3.18 for i686-pc-linux-gnu
2004-06-25 13:19:47 [http://setiathome.berkeley.edu/] Project prefs: using your defaults
2004-06-25 13:19:47 [http://setiathome.berkeley.edu/] Host ID not assigned yet
2004-06-25 13:19:47 [---] No general preferences found - using BOINC defaults
2004-06-25 13:19:47 [---] Running CPU benchmarks
2004-06-25 13:19:47 [---] Suspending computation and network activity - running CPU benchmarks
2004-06-25 13:20:03 [---] Received signal 15
2004-06-25 13:20:03 [---] Received signal 15
Killed
p35394547:/kunden/homepages/14/d38373691/htdocs/seti > ./boinc318
2004-06-25 13:21:02 [---] Starting BOINC client version 3.18 for i686-pc-linux-gnu
2004-06-25 13:21:02 [http://setiathome.berkeley.edu/] Project prefs: using your defaults
2004-06-25 13:21:02 [http://setiathome.berkeley.edu/] Host ID not assigned yet
2004-06-25 13:21:02 [---] No general preferences found - using BOINC defaults
2004-06-25 13:21:02 [---] Running CPU benchmarks
2004-06-25 13:21:02 [---] Suspending computation and network activity - running CPU benchmarks
2004-06-25 13:22:01 [---] Received signal 15
Killed
p35394547:/kunden/homepages/14/d38373691/htdocs/seti >
***

The hotline said, this is a security mechanism because
BOINC bind all server-IPs to himself. [German text: Dabei handelt es sich um einen Sicherheitsmechanismus Ihres Managed-Servers.
(Dienste, die sich an _alle_ IPs des Servers binden, werden beendet).]
Is there any solution?

(PS: Excuse my bad english)

Malte

My guess is that there will be no way around that.

Even if you get past the IP binding, most managed servers will not allow cpu intensive processes to run for any length of time at all - it will interpret it as a runaway process and kill it every time it starts up.

> Even if you get past the IP binding, most managed servers will not allow cpu
> intensive processes to run for any length of time at all - it will interpret
> it as a runaway process and kill it every time it starts up.

That is no problem, my server do not have any process time restrictions. Old Seti@Home run perfectly over a couple of month.

Malte