Score:0

application runs from command line, but cannot start as init.d script - openWrt

by flag

Got a problem with my service written in C. It runs as an init.d service and has been working fine for many months on many devices. Today I've made some changes in the software and very strange thing occurs. I upgraded the package and noticed that it does not start by init.d, but when I try to run it invoking the command manually it runs perfectly well. That application gives a lot of diagnostic information to the console, but I am not able to see its output when trying to run it as a service. Is there any way to log the output of an application run as an init.d service?

Kal

Score:1
lk flag

There are logging/debugging facilities in OpenWrt.

Set PROCD_DEBUG=1 to see debugging information when starting or stopping a procd init script. Also, INIT_TRACE=1 /etc/init.d/mything $action Where $action is start/stop etc.

More information could be found in OpenWrt wiki.

Kal800 avatar
by flag
thanks, spotted
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.