Need to start a reliable, persistent server

[Tim Mensch]

I'm working with a client who needs to have a persistent server run on
a device running Android. The device will be wall-powered, so battery
life is not an issue.

The server is written in portable C/C++ code. I'm well on the way to
getting it all to build on Android, but I'm worried about what I've
heard about Android killing off processes it "doesn't know about."

If I start this process in init.rc, is that all I need to do to
guarantee it will start on boot and stick around indefinitely?

Thanks,

Tim Mensch

[Glenn Kasten]

Yes - you could make it a service (in the init sense of the term), and
put it in an "on restart" clause in the servicemanager section of
init.rc. For an example see mediaserver.

[Chris Stratton]

You probably also want to give it special oom killer values to protect it. 

[Zoltan Kuscsik]

Hi,

mission critical services should be written in native code and started by the

init.rc or system server. 

Z

--
unsubscribe: android-porti...@googlegroups.com
website: http://groups.google.com/group/android-porting

[Tim]

Yes, it will be written in native code, and I was planning on using init.rc. I'm not sure what you mean by the "system server," but init.rc should work fine, thanks.

Tim

On Sunday, March 4, 2012 2:01:28 PM UTC-7, zoli2k wrote:

Hi,

mission critical services should be written in native code and started by the

init.rc or system server. 

Z

On Sun, Mar 4, 2012 at 5:37 PM, Glenn Kasten wrote:

Yes - you could make it a service (in the init sense of the term), and
put it in an "on restart" clause in the servicemanager section of
init.rc. For an example see mediaserver.

On Mar 2, 5:07 pm, Tim Mensch  wrote: