On Feb 15, 7:44 pm, Dianne Hackborn <hack...@android.com> wrote:
> No, it is not, it is done by the OOM killer in the kernel.  It decides what
> to kill first based on the oom_adj, with higher numbers killed before lower
> ones.  The foreground process is oom_adj 0, the least needed process is 16,
> system processes are < 0.

Too much unix on the brain.   I imagined that a process which made
ttys available
to the rild from init.rc to not have to do any interactions with the
android service
architecture.

What would a native arm binary have to do to be considered a system
process
when started from init.rc? (I get that android:persistent set to true
in the
manifest probably does it for things with a manifest.)

Given that one of those two things happens, is it safe to say such a
process
is only in competition with other init processes and anything with
android:persistent
set to true in it's manifest (and the original poster doesn't need to
worry about some
app getting their native service killed)?

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

Reply via email to