Re: [PATCH v3] procd: add procd json output to init

2020-12-17 Thread Petr Štetiar
Florian Eckert [2020-12-17 10:34:25]: > So that I do not always have to type the whole string. Well, you don't need to. root@OpenWrt:/# cat ~/.shinit procd_service_list() { ubus call service list "{'name':\"$1\",'verbose':true}" } root@OpenWrt:/# procd_service_list urngd {

Re: [PATCH v3] procd: add procd json output to init

2020-12-17 Thread Florian Eckert
Hello Petr On 2020-12-17 10:12, Petr Štetiar wrote: Florian Eckert [2020-12-17 09:40:08]: With this change, the init script is now extend with the command to get this information easier. I still lack the information about your use case, how do you use this output of this command.

Re: [PATCH v3] procd: add procd json output to init

2020-12-17 Thread Petr Štetiar
Florian Eckert [2020-12-17 09:40:08]: Hi, > By adding the extra command `procd` it is now possible to retrieve all > relevant data from a procd started service directly via the init script. > > Until now, you have to query the ubus to get the information with the > following command. > >

[PATCH v3] procd: add procd json output to init

2020-12-17 Thread Florian Eckert
By adding the extra command `procd` it is now possible to retrieve all relevant data from a procd started service directly via the init script. Until now, you have to query the ubus to get the information with the following command. `ubus call service list '{"name":"","verbose":true}'` With