Hi Denys, On Sat, Dec 03, 2016 at 04:09:05PM +0100, Denys Vlasenko wrote: > On Sat, Dec 3, 2016 at 2:25 PM, Jo-Philipp Wich <j...@mein.io> wrote: > > Hi Denys, > > > >> Well, we certainly can fix the ntpd start scritps, > >> but this is a generic problem, right? We'd want ANY > >> daemons to be run "properly", with their output logged. > >> With log size and location controlled. With log rotation. > >> Etc. etc etc. > > > > Controlling log rotation, sizes etc. is the task of the syslog > > implementation, not of the service supervisor imho. > > That works only if you decide to log messages from all daemons > together (be it syslog or something else). > > In many cases, I would rather have each daemon log to a separate > store. This way, a flood of messages from one daemon can never > cause system to lose important log output of another daemon: > logs are rotated *independently*.
Sound reasonable, but afaik not yet implemented. > > The following init script parameters will cause the stdio messages to > > get redirected to syslog: > > > > procd_set_param stdout 1 > > procd_set_param stderr 1 > > This works, thanks. I see the log in web interface. > BTW, how to cat syslog from openwrt command line? You should use: logread Cheers Daniel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
