table of contents
- bookworm 246.10-1debian1
- testing 246.10-1debian1
- unstable 246.10-1debian1
- experimental 252.9-1debian1
SD_BUS_INTERFACE_NAME_IS_VALID(3) | sd_bus_interface_name_is_valid | SD_BUS_INTERFACE_NAME_IS_VALID(3) |
NAME¶
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
SYNOPSIS¶
#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);
DESCRIPTION¶
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.
RETURN VALUE¶
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.
Errors¶
Returned errors may indicate the following problems:
-EINVAL
NOTES¶
These APIs are implemented as a shared library, which can be compiled and linked to with the libelogind pkg-config(1) file.
SEE ALSO¶
elogind(1), sd-bus(3), sd_bus_call_method(3)
elogind 246.10 |