This is normal. Eclipse does start the adb daemon on start but never
kills it (unless it is to restart it right after).
The reason is that we cannot be sure that quitting Eclipse means you
don't have a shell/command prompt that is currently running some adb
commands (such as a shell on the device). You wouldn't like it if
those commands were interrupted because we killed the adb daemon.
Xav
On Tue, May 4, 2010 at 6:06 PM, Ubuntu Explorer
wrote:
> Hi,
>
> Even after closing eclipse, adb still alive. Has anyone seen this issue
> before?
>
> ps -aef | grep adb
> 1464 1 0 08:28 ? 00:00:02 adb fork-server server
>
> Regards,
> UE
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Beginners" group.
>
> NEW! Try asking and tagging your question on Stack Overflow at
> http://stackoverflow.com/questions/tagged/android
>
> To unsubscribe from this group, send email to
> android-beginners+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-beginners?hl=en
>
--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
Please do not send me questions directly. Thanks!
--
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
NEW! Try asking and tagging your question on Stack Overflow at
http://stackoverflow.com/questions/tagged/android
To unsubscribe from this group, send email to
android-beginners+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
