[From nobody Thu Jun 25 05:54:12 2020
X-policyd-weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5
 CL_IP_EQ_HELO_IP=-2 (check from: .kitschensync. - helo: .mailout.easymail. -
 helo-domain: .easymail.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7
Received: from mailout.easymail.ca (mailout.easymail.ca [64.68.201.169])
 by arrakis.dune.hu (Postfix) with ESMTPS
 for &lt;openwrt-devel@lists.openwrt.org&gt;; Tue,  8 Mar 2016 21:22:56 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
 by mailout.easymail.ca (Postfix) with ESMTP id BB9B4E37C;
 Tue,  8 Mar 2016 15:22:46 -0500 (EST)
X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 required=5 tests=[ALL_TRUSTED=-1.8,
 AWL=-0.084, BAYES_05=-1.11, DNS_FROM_AHBL_RHSBL=0.692,
 STOX_REPLY_TYPE=0.001]
Received: from mailout.easymail.ca ([127.0.0.1])
 by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new,
 port 10024)
 with ESMTP id G9Zif8YDPcPA; Tue,  8 Mar 2016 15:22:45 -0500 (EST)
Received: from twonky7 (pool-98-118-10-131.bstnma.fios.verizon.net
 [98.118.10.131]) (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mailout.easymail.ca (Postfix) with ESMTPSA id 90122E460;
 Tue,  8 Mar 2016 15:22:41 -0500 (EST)
Message-ID: &lt;6E201D805DEF4D3993D6C1873A5AB6AE@fortmeadow.com&gt;
From: &quot;Ted Hess&quot; &lt;thess@kitschensync.net&gt;
To: &quot;OpenWrt developers&quot; &lt;openwrt-devel@lists.openwrt.org&gt;
Cc: &lt;blogic@openwrt.org&gt;
Subject: procd warning about respawn
Date: Tue, 8 Mar 2016 15:22:41 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=&quot;utf-8&quot;; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331

@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 

]