同步操作将从 OpenHarmony/docs 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
Problem
During system startup, the error message "[Init] InitReadCfg, parse failed! please check file /etc/init.cfg format." is displayed, and the startup is interrupted, as shown in the following figure.
Cause
During the modification of the init.cfg file, required commas (,) or parentheses are missing or unnecessary ones are added. As a result, the file's JSON format becomes invalid.
Solution
Check the init.cfg file and ensure that its format meets the JSON specifications.
Problem
After the image burning is complete, the system keeps restarting.
Cause
Each service started by the init process has the importance attribute, as described in Table 3 in Job Management.
During the startup of a service whose importance is 1, if the service exits due to a process crash or an error, the init process automatically restarts the development board.
Solution
Problem
Calling the SetParameter or GetParameter API fails even if correct values are passed to all input parameters.
Cause
Permission verification has been enabled for the SetParameter and GetParameter APIs. If the UID of the caller is greater than 1000, that is, the caller does not have the permission to call these APIs, API calls will fail even if the parameters are correct.
Solution
No action is required.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。