libvirt

mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-23 14:15:28 +00:00

History

Daniel P. Berrangé 1519c55dc8 rpc: avoid unlinking sockets passed in from systemd Currently the socket code will unlink any UNIX socket path which is associated with a server socket. This is not fine grained enough, as we need to avoid unlinking server sockets we were passed by systemd. To deal with this we must explicitly track whether each socket needs to be unlinked when closed, separately of the client vs server state. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>		2019-07-12 16:55:39 +01:00
..
input-data-admin-server-names.json
input-data-admin.json
input-data-anon-clients.json
input-data-client-auth-pending-failure.json
input-data-client-auth-pending.json
input-data-client-ids.json
input-data-client-timestamp.json
input-data-initial.json
input-data-no-keepalive-required.json
output-data-admin-server-names.json
output-data-admin.json
output-data-anon-clients.json
output-data-client-auth-pending.json
output-data-client-ids.json
output-data-client-timestamp.json
output-data-initial.json
output-data-no-keepalive-required.json
README

README

   virnetservertest data files
   ===========================

The various input-data-*.json files are a record of all the historical
formats that libvirt has been able to produce data for. Everytime a
new field is added to the JSON output, a *new* input data file should
be created. We must not add new fields to existing input-data files,
nor must we ever re-structure them if code changes, as we must check
new code handles the legacy formats.

The various output-data-*.json files are the record of what the *new*
JSON output should look like for the correspondingly named input-data
file. It is permissible to change the existing output-data-*.json
files if the format we save in is updated.