On 2018-01-17 11:11, Karl Vogel wrote:
John Crispin writes:
On 17/01/18 10:54, Koen Vandeputte wrote:
On 2018-01-17 10:43, Karl Vogel wrote:
Shows how long an initd task took, for example:
procd: stop /etc/init.d/dropbear running - took 0.088824s
procd: Update service dnsmasq
procd
John Crispin writes:
> On 17/01/18 10:54, Koen Vandeputte wrote:
>>
>>
>> On 2018-01-17 10:43, Karl Vogel wrote:
>>> Shows how long an initd task took, for example:
>>>
>>> procd: stop /etc/init.d/dropbear running - took 0.088824s
>>> procd: Update service dnsmasq
>>> procd: Update instance d
On 17/01/18 10:54, Koen Vandeputte wrote:
On 2018-01-17 10:43, Karl Vogel wrote:
Shows how long an initd task took, for example:
procd: stop /etc/init.d/dropbear running - took 0.088824s
procd: Update service dnsmasq
procd: Update instance dnsmasq::dnsmasq
procd: running /etc/init.d
On 2018-01-17 10:43, Karl Vogel wrote:
Shows how long an initd task took, for example:
procd: stop /etc/init.d/dropbear running - took 0.088824s
procd: Update service dnsmasq
procd: Update instance dnsmasq::dnsmasq
procd: running /etc/init.d/dnsmasq running
procd: start /etc/init.d/d
Shows how long an initd task took, for example:
procd: stop /etc/init.d/dropbear running - took 0.088824s
procd: Update service dnsmasq
procd: Update instance dnsmasq::dnsmasq
procd: running /etc/init.d/dnsmasq running
procd: start /etc/init.d/dnsmasq running
procd: stop /etc/init.d/dnsmasq
