On 11 June 2015 at 14:32, Nikos Mavrogiannopoulos <n...@gnutls.org> wrote: > In issue 574 [0] there is a big discussion of the behavior of > transmission in openwrt. To summarize it: > * By default when transmission downloads, it may crash the router due to > high memory consumption and OOB. That crash may lead to reboot or not. > * To avoid that, some memory limitations can be set (such as disabling > overcommit), and then transmission will exit, but the router would be > functional. > > I think the 2nd is quite a reasonable approach as it is more important > to keep the router up and running than transmission (or any other > individual service). However, a way to reduce the impact would be for > netifd to restart transmission if crashed. Can that be done already, or > inittab is the only option? >
Migrate transmission to procd for service management. Use `procd_set_param respawn` to define the respawn behaviour. As for resource limit, there is also a `procd_set_param limits`, but i have never tried it myself [0]. The yet-to-be-implemented cgroups support of procd may also help [1] :) [0] procd limits usage, https://lists.openwrt.org/pipermail/openwrt-devel/2015-January/030351.html [1] adding seccomp and service jailing to procd, https://lists.openwrt.org/pipermail/openwrt-devel/2015-March/032197.html yousong > regards, > Nikos > > [0]. https://github.com/openwrt/packages/issues/574 > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
