mirror of
https://github.com/servalproject/serval-dna.git
synced 2025-04-03 17:19:08 +00:00
5cbc2167ec
Add sqlite_exec_void_retry() function, use it in rhizome_update_file_priority(). This should be reviewed to ensure that the server process never sleeps. The general problem remains of what the servald process should do if the database is locked when it tries to update. Simplest solution is to sleep and retry, but that blocks all other services and would hurt VoMP. A better solution would be for each Rhizome operation to collect its database updates into a single transaction and place that in a work queue that gets called using schedule() (or even watch() if a file-descriptor event can somehow be used when the database becomes available). Another solution is perhaps to perform all Rhizome operations in a dedicated process that can block indefinitely on the database without affecting servald responsiveness.
@PGS/20120615 Sometimes it is helpful to run more than one servald instance on a given machine for debugging purposes. To make this easier, there is a dummy interface driver that servald knows about. To use it: 1. create an empty file, e.g., dummynet0, somewhere convenient 2. For each servald instance you wish to use it, set the interface specification to include the dummynet file. Use a specification like "+>pathtodummynetfile", where pathtodummynetfile is the relative path from the instance path of that servald instance to the dummynet file. For example, you might run: % servald config set interfaces "+eth0,+>../dummynet0" 3. Run each servald instance. They should now use the dummy network. NOTE: Because dummynets are files, not sockets, poll/select does not work on them. As a result the main overlay loop has slightly different behaviour and timing characteristics when a dummynet is in use. TODO: Convert dummynet interface to use a unixdomain socket, and a simple dummynet server that reflects packets among the clients connected, so that all socket semantics (including use of poll/select) are preserved.