| commit | 509b2e527564afbf9d905ba14430cea1dbea46ef | [log] [tgz] |
|---|---|---|
| author | Chandramohan Harkude <chandramohan.harkude@gmail.com> | Tue Aug 12 01:08:38 2025 +0530 |
| committer | Chandra Harkude <Chandramohan.harkude@gmail.com> | Mon Aug 18 07:25:12 2025 +0000 |
| tree | e67ad5c616fe4fc84fe0f4562c22631e79777d7a | |
| parent | 92c4806df185d629145a3ad3801a208a445af6fd [diff] |
Add error for NTP server property It is observed that on passing invalid arguments to configure NTP servers phosphor-netword is crashing because it is not throwing the invalid argument exception To address the issue adding error invalid argument as it is not present currently. The MRs created for returning invalid argument are below https://gerrit.openbmc.org/c/openbmc/phosphor-networkd/+/82694 and https://gerrit.openbmc.org/c/openbmc/bmcweb/+/82696 Change-Id: Iebd09b482d0938c614d87e9cbd8fa1b765e0309a Signed-off-by: Chandramohan Harkude <chandramohan.harkude@gmail.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.
This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.
The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir