Attached to Project: OpenWrt/LEDE Project Opened by Sven Kux - 17.06.2018 Last edited by Adrian Schmutzler - 19.06.2020 FS#1591 - procd: May hangs during reboot because of netdevice reference counter imbalance
This article may require cleanup to meet Wikipedia's quality standards.The specific problem is: Active distributions composed entirely of free software (Dragora GNU/Linux-Libre, gNewSense, Guix System, LibreCMC, Musix GNU+Linux, Parabola GNU/Linux-libre, and Trisquel) need information in all sub categories, #General is complete.
procd_set_param user nobody Default OpenWrt only has a ‘root’ user or ‘nobody’ as the process owner. You can add users with the usual linux way, see Create a non-privileged user in OpenWrt or if you are creating an actual package you can use buildpackage defines to make OpenWrt generate the user when the package is installed.
02.09.2019 · procd is the OpenWrt process management daemon written in C. It keeps track of processes started from init scripts (via ubus calls), and can suppress redundant service start/restart requests when the config/environment has not changed. procd has replaced … , e.g. hotplug2, a dynamic device management subsystem for embedded systems.
service: add reload_signal property Introduce a new optional property "reload_signal" which - if set - instructs procd to not terminate and restart supervised processes upon changes, but to send them a kill() signal instead. This is useful for services which fully support native config reload upon receipt of a signal. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
0 does not change this and kill -9 $$ also does not trigger a restart. What i'am doing wrong? when reading https://wiki.openwrt.org/inbox/procd-init-scripts
description, OpenWrt service / process manager. owner, Git. last change, Sun, 19 Dec 2021 18:16:30 -0800 ... URL, https://git.openwrt.org/project/procd.git.
10.08.2021 · OpenWrt comes with a procd_send_signal () helper that doesn't require passing PID directly. Example: reload_service () { procd_send_signal service_name [instance_name] [signal] } The signal argument is SIGHUP by default and must be specified by NAME. You can get available signals using kill -l .