I was wondering why the loggers (except ubox) are all started as priority 20 (same as “network”):
$ grep START= package/system/ubox/files/log.init feeds/packages/net/ulogd/files/ulogd.init feeds/packages/net/rsyslog/files/rsyslog.init feeds/packages/admin/syslog-ng/files/syslog-ng.init package/system/ubox/files/log.init:START=12 feeds/packages/net/ulogd/files/ulogd.init:START=20 feeds/packages/net/rsyslog/files/rsyslog.init:START=20 feeds/packages/admin/syslog-ng/files/syslog-ng.init:START=20 $ seems to me that (a) there’s no dependency on the network service being up before the logger starts, since it uses an unbound socket anyway (and hence will do the right thing if more interfaces are added, deleted, or otherwise changed) and (b) it’s entirely possible that at some point we might want to add logging to earlier startup scripts or services, such as S19dhcpd (also started before the network comes up)… I’ve played with starting syslog-ng at level 12 (same as box’s logger) and it had no obvious ill-effects. Anyone see any reason to not proceed with changing it? Thanks, -Philip _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
