Actually, gnunet-arm behaves like any other gnunet-<service> binary: If <service> is not running, it will still try and communicate with <service> which will lead to it hanging unless ARM automatically starts the service. Now, ARM cannot automatically start itself, as that is actually its own job. So this is kind of a chicken/egg situation.
We could abuse the ARM start functionality (GNUNET_ARM_request_service_start) when stopping. If we call that function on "stop" in any case, it is a NOP before stop. Else we start before the stop. Not pretty, but might improve the UX. BR > On 25. Sep 2019, at 16:02, xrs <[email protected]> wrote: > > Signed PGP part > Hi all, > > I stumple upon a problem that always got into my way when using > gnunet-arm: If the services are not running and I execute gnunet-arm -e > it hangs. How about ending it normally with some exit code >0? > > cheers, > xrs > >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
