史上最强Android保活思路：深入剖析腾讯TIM的进程永生技术(11)

这个应该就是TIM进程自身实现了一套执行startService的Binder调用，向Binder驱动发送 BINDER_WRITE_READ的ioctl命令。 再然后发送kill SIGKILL将自身MSF进程杀掉，同样的道理可以再次被拉起。
分析到这里，看执行了writev操作， 应该就是Log操作， 有一个关键词到 Watermelon 吸引了我的注意力， 搜索 Watermelon 关键词，果然找到新的一片天地。
6.4 TIM日志
//旧的MSF进程24538 24562 D Watermelon: lock filesuccess >> /data/user/0/com.tencent.tim/app_indicators/indicator_p224538 24562 E Watermelon: Watch >>>>Daemon<<<<< Daed !!24538 24562 E Watermelon: java_callback:onDaemonDead24538 24562 V Watermelon: onDaemonDead24576 24576 D Watermelon: lock filesuccess >> /data/user/0/com.tencent.tim/app_indicators/indicator_d124576 24576 E Watermelon: Watch >>>>Daemon<<<<< Daed !!24576 24576 E Watermelon: process exit//新daemon进程25103 25103 V Watermelon: initDaemon processName=com.tencent.tim:Daemon25103 25103 E Watermelon: onDaemonAssistantCreate25134 25134 D Watermelon: start daemon24=/data/user/0/com.tencent.tim/app_bin/daemon2//app_d进程25137 25137 D Watermelon: pipe readdatasize >> 316 <<25137 25137 D Watermelon: indicator_self_path >> /data/user/0/com.tencent.tim/app_indicators/indicator_d125137 25137 D Watermelon: observer_daemon_path >> /data/user/0/com.tencent.tim/app_indicators/observer_p125137 25137 I Watermelon: sIActivityManager==NULL25137 25137 I Watermelon: BpActivityManager init//新daemon25103 25120 D Watermelon: start try to lock file>> /data/user/0/com.tencent.tim/app_indicators/indicator_p225103 25120 D Watermelon: lock filesuccess >> /data/user/0/com.tencent.tim/app_indicators/indicator_p225137 25137 I Watermelon: BpActivityManager init end//app_d进程25137 25137 D Watermelon: start try to lock file>> /data/user/0/com.tencent.tim/app_indicators/indicator_d125137 25137 D Watermelon: lock filesuccess >> /data/user/0/com.tencent.tim/app_indicators/indicator_d1//新MSF进程25119 25119 V Watermelon: initDaemon processName=com.tencent.tim:MSF25119 25119 V Watermelon: mConfigurations.PERSISTENT_CONFIG.PROCESS_NAME=com.tencent.tim:MSF25119 25119 E Watermelon: onPersistentCreate25153 25153 D Watermelon: start daemon24=/data/user/0/com.tencent.tim/app_bin/daemon225119 25144 D Watermelon: pipe write len=32425159 25159 D Watermelon: pipe readdatasize >> 324 <<25159 25159 D Watermelon: indicator_self_path >> /data/user/0/com.tencent.tim/app_indicators/indicator_p125159 25159 D Watermelon: observer_daemon_path >> /data/user/0/com.tencent.tim/app_indicators/observer_d125159 25159 I Watermelon: sIActivityManager==NULL25159 25159 I Watermelon: BpActivityManager init25119 25144 D Watermelon: start try to lock file>> /data/user/0/com.tencent.tim/app_indicators/indicator_d225119 25144 D Watermelon: lock filesuccess >> /data/user/0/com.tencent.tim/app_indicators/indicator_d225159 25159 I Watermelon: BpActivityManager init end//各进程进入监听就绪状态25159 25159 D Watermelon: start try to lock file>> /data/user/0/com.tencent.tim/app_indicators/indicator_p125159 25159 D Watermelon: lock filesuccess >> /data/user/0/com.tencent.tim/app_indicators/indicator_p125119 25144 E Watermelon: Watched >>>>OBSERVER<<<< has been ready...25119 25144 D Watermelon: start try to lock file>> /data/user/0/com.tencent.tim/app_indicators/indicator_p225159 25159 E Watermelon: Watched >>>>OBSERVER<<<< has been ready...25159 25159 D Watermelon: start try to lock file>> /data/user/0/com.tencent.tim/app_indicators/indicator_d125137 25137 E Watermelon: Watched >>>>OBSERVER<<<< has been ready...25137 25137 D Watermelon: start try to lock file>> /data/user/0/com.tencent.tim/app_indicators/indicator_p125103 25120 E Watermelon: Watched >>>>OBSERVER<<<< has been ready...25103 25120 D Watermelon: start try to lock file>> /data/user/0/com.tencent.tim/app_indicators/indicator_d2