View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011714 | GNUnet | ARM service | public | 2026-08-06 10:52 | 2026-08-07 10:15 |
| Reporter | Jllx | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | Git master | ||||
| Summary | 0011714: gnunet-arm -I never returns if no service are running | ||||
| Description | when trying to know if the services are running I do a "gnunet-arm -I" which never returns if there is no service running (have to kill the process) | ||||
| Steps To Reproduce | with no service running : gnunet-arm -I if service is running (previous step did reply): gnunet-arm -e && gnunet-arm -I | ||||
| Tags | No tags attached. | ||||
|
|
This is also true for gnunet-arm -e, btw. Not sure if that can be fixed. We could timeout I guess. |
|
|
Maybe to clarify: All CLI tools that interact with gnunet services do not "hang". They wait for the service to come online (again) to talk to them. You can ctrl-c out of this. So this issue only has 2 solutions: 1. Close as wontfix 2. Think about adding a (delayed) info message to affected CLI utilities (quite a few of those) that tell the user that gnunet may not be running. |
