Spam detection software, running on the system "arrakis.dune.hu",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview:  @blogic – rather than continue this on a closed Github PR...
   Since changeset (https://dev.openwrt.org/changeset/48915), 
procd_close_instance
   issues a WARNING about respawn not defined if 'procd_set_param respawn' is
   not in ones startup script. [...] 

Content analysis details:   (6.0 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 1.9 STOX_REPLY_TYPE        No description available.
 3.1 STOX_REPLY_TYPE_WITHOUT_QUOTES No description available.
 1.0 XPRIO                  Has X-Priority header


--- Begin Message ---
@blogic – rather than continue this on a closed Github PR...

Since changeset (https://dev.openwrt.org/changeset/48915), procd_close_instance issues a WARNING about respawn not defined if 'procd_set_param respawn' is not in ones startup script.

Is respawn now a required parameter or is this an extraneous buglet?

Example:

root@OpenWrt:~# /etc/init.d/squeezelite start
WARNING: Variable 'respawn' does not exist or is not an array/object
root@OpenWrt:~#

/ted
--- End Message ---
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to