Re: [OpenWrt-Devel] uhttpd / startup-error without a message
Hi, this is already fixed in trunk. The uhttpd stderr is relayed to syslog there. ~ Jow ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] uhttpd / startup-error without a message
today I was searching for a non-running uhttpd and recognized, that there are no error messages anymore if something goes wrong. in 62ff68fb / r38023 # procd: convert various packages to procd style init.d scripts # Signed-off-by: John Crispin blo...@openwrt.org the debug-output was commented out. was this intended? (see line 135 in package/network/services/uhttpd/files/uhttpd.init) bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] uhttpd / startup-error without a message
* Jo-Philipp Wich j...@openwrt.org [11.05.2015 10:29]: this is already fixed in trunk. The uhttpd stderr is relayed to syslog there. thank you - i see: this is not very intuitive. can this be send to console when user is interactive? (like: loggger -s message) bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] uhttpd / startup-error without a message / procd interactive logging
* Jo-Philipp Wich j...@openwrt.org [11.05.2015 11:47]: this is not very intuitive. can this be send to console when user is interactive? (like: loggger -s message) Not easily as it is procd logging the services stderr. One can implement a test or debug start action though which would calculate the commandline and start the daemon in foreground without actually registering it with procd. it think thats too special - there should be a generic way to get direct feedback on the commandline when something fails without doing magic. what if we e.g. 'export INTERACTIVE=1' via /etc/profile so procd / a called script is aware of this? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] uhttpd / startup-error without a message / procd interactive logging
it think thats too special - there should be a generic way to get direct feedback on the commandline when something fails without doing magic. what if we e.g. 'export INTERACTIVE=1' via /etc/profile so procd / a called script is aware of this? Whats too special with /etc/init.d/$SERVICE debug ? Its exactly doing what you'd normally do to hunt down the error - start the service in foreground so you need to kill with Ctrl-C. All messages are sent to the console then (at least in the case of uhttpd or any other service using ulog). ~ Jow ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] uhttpd / startup-error without a message
Hi. thank you - i see: this is not very intuitive. can this be send to console when user is interactive? (like: loggger -s message) Not easily as it is procd logging the services stderr. One can implement a test or debug start action though which would calculate the commandline and start the daemon in foreground without actually registering it with procd. ~ Jow ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] uhttpd / startup-error without a message / procd interactive logging
* Jo-Philipp Wich j...@openwrt.org [11.05.2015 12:34]: it think thats too special - there should be a generic way to get direct feedback on the commandline when something fails without doing magic. what if we e.g. 'export INTERACTIVE=1' via /etc/profile so procd / a called script is aware of this? Whats too special with /etc/init.d/$SERVICE debug ? it has to be implemented for every service - or are you thinking of doing it generic via rc.common? (then I am fine with 'debug') also: if the service fails to start, there should be at least a 'hint-message' to use 'debug'. bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
