Lines Matching full:daemon
1 THE ANDROID "QEMUD" MULTIPLEXING DAEMON
6 The Android system image includes a small daemon program named "qemud"
54 'qemud' daemon started at boot by /system/etc/init.goldfish.rc
56 The daemon also opens an emulated serial port (e.g. /dev/ttyS1) and
76 Where each client gets a 'channel' number allocated by the daemon
87 Channel 0 is reserved for control messages between the daemon and the
91 name to the daemon, the later sends to the emulator:
115 But if the client disconnects from the socket, the daemon will
121 a client, the emulator will send to the daemon (on channel 0):
125 The daemon deals with this gracefully (e.g. it will wait that the
126 client has read all buffered data in the daemon before closing the
129 - Any other command sent from the daemon to the emulator will result
143 The daemon's source is in $ROOT/development/emulator/qemud/qemud.c
177 implement an older variant of the qemud daemon that uses a slightly
183 The old scheme also used a serial port to allow the daemon and the emulator
215 - the daemon created a de-facto numbered channel for each one of these
220 it implements, e.g. it would send *to* the daemon on channel 0:
226 (Note that on the current implementation, the daemon is sending connection
229 - the daemon would respond with either:
239 This old scheme was simpler to implement in both the daemon and the emulator
243 as well as the daemon source file (which contained a hard-coded list
