The current message mentions a "server" which can give the misleading
impression that the UI is waiting for a remote network server. The delay
is actually in waiting for the pb-discover process to be ready, so
update the message to reflect that.
Signed-off-by: Samuel Mendoza-Jonas <sam@mendozajonas.com>
(cherry picked from commit
ea8bd5f424a9b01c71e1694bb5b6ffc13e3da4f5)
if (!cui->client) {
waiter_register_timeout(cui->waitset, 1000, cui_server_wait,
cui);
if (!cui->client) {
waiter_register_timeout(cui->waitset, 1000, cui_server_wait,
cui);
- nc_scr_status_printf(cui->current, "Info: Waiting for server");
+ nc_scr_status_printf(cui->current,
+ "Info: Waiting for device discovery");
- nc_scr_status_printf(cui->current, "Info: Connected to server!");
+ nc_scr_status_printf(cui->current,
+ "Info: Connected to pb-discover!");
talloc_steal(cui, cui->client);
if (cui->has_input) {
talloc_steal(cui, cui->client);
if (cui->has_input) {
- pb_log("Aborting default boot on server connect\n");
+ pb_log("Aborting default boot on pb-discover connect\n");
discover_client_cancel_default(cui->client);
}
}
discover_client_cancel_default(cui->client);
}
}