MigrationHelper::Migrate does not migrate /data/system/ndebugsocket |
|||
Issue descriptionCurrently, MigrationHelper cannot handle sockets and it silently deletes /data/system/ndebugsocket. We should make sure that this behavior is OK, or support migrating sockets.
,
Apr 26 2017
I remember bringing this up before and being told that the sockets should not need to persist after a reboot, but I haven't confirmed this myself.
,
Apr 27 2017
I think sockets can be recreated so it should be OK to silently delete them, but wanted to have discussion recorded somewhere. My main concern is if /data/system/ndebugsocket is the only socket we may encounter or not.
,
Apr 27 2017
So this is stale UNIX domain socket that is not backed by a running app anymore? I suspect whatever will recreate the socket at boot. Is this /data/system/ndebugsocket/sock on N? kevin_cheets:/data/system # ls -l ndebugsocket/sock srwx------ 1 system system 0 2017-04-27 14:00 ndebugsocket/sock
,
Apr 27 2017
I wanted to check my hypothesis, but I thought fuser would show me who's using it but nothing is shown. hmm localhost ~ # fuser -v -a /home/root/s_h_o_u/android-data/data/system/ndebugsocket/sock
,
Apr 27 2017
netstat -l -p inside container tells me (hmm why does android-sh not have the permission to see the process that's listening ?): unix 2 [ ACC ] STREAM LISTENING 21998 - /data/system/ndebugsocket/sock deleting the file and logging in again ends up recreating the file as expected.
,
May 10 2017
close as working as intended? |
|||
►
Sign in to add a comment |
|||
Comment 1 by hashimoto@chromium.org
, Apr 26 2017