DOKK / manpages / debian 12 / libelogind-dev-doc / sd_bus_interface_name_is_valid.3.en
SD_BUS_INTERFACE_NAME_IS_VALID(3) sd_bus_interface_name_is_valid SD_BUS_INTERFACE_NAME_IS_VALID(3)

sd_bus_interface_name_is_valid, sd_bus_service_name_is_valid, sd_bus_member_name_is_valid, sd_bus_object_path_is_valid - Check if a string is a valid bus name or object path

#include <elogind/sd-bus.h>

int sd_bus_interface_name_is_valid(const char* p);

int sd_bus_service_name_is_valid(const char* p);

int sd_bus_member_name_is_valid(const char* p);

int sd_bus_object_path_is_valid(const char* p);

sd_bus_interface_name_is_valid() checks if a given string p is a syntactically valid bus interface name. Similarly, sd_bus_service_name_is_valid() checks if the argument is a valid bus service name, sd_bus_member_name_is_valid() checks if the argument is a valid bus interface member name, and sd_bus_object_path_is_valid() checks if the argument is a valid bus object path. Those functions generally check that only allowed characters are used and that the length of the string is within limits.

Those functions return 1 if the argument is a valid interface / service / member name or object path, and 0 if it is not. If the argument is NULL, an error is returned.

Returned errors may indicate the following problems:

-EINVAL

The p parameter is NULL.

These APIs are implemented as a shared library, which can be compiled and linked to with the libelogind pkg-config(1) file.

elogind(1), sd-bus(3), sd_bus_call_method(3)

elogind 246.10