It is possible, and quality patches are gladly accepted, to be sent at
b.android.com
The code you're looking for is at external/qemu/android/utils/filelock.c
On Tue, Apr 13, 2010 at 8:07 PM, Dmitry Golubovsky <golubov...@gmail.com>wrote:
> OK, finally strace gave me this:
>
> lstat64("/home/dima/.android/avd/AVD-1.avd/userdata-
> qemu.img.tmp-6p9Pnr", {st_mode=S_IFREG|0600, st_size=6, ...}) = 0
> link("/home/dima/.android/avd/AVD-1.avd/userdata-qemu.img.tmp-6p9Pnr",
> "/home/dima/.android/avd/AVD-1.avd/userdata-qemu.img.lock") = -1
> ENOSYS (Function not implemented)
>
> and several other attempts to call "link" that also fail (sshfs does
> not support hard links).
>
> Is it possible to change the emulator's behavior to create lock files
> somewhere in /tmp (using some hash of image path as lock file name)? I
> am OK to try this myself: which repositories from
> https://android.git.kernel.org/
> are necessary to rebuild the emulator alone, and where in the sources
> is the code responsible for image locks?
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>
> To unsubscribe, reply using "remove me" as the subject.
>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
