diff --git a/man/udev_device_has_tag.xml b/man/udev_device_has_tag.xml index 9c64a4b45b..2e5b67e750 100644 --- a/man/udev_device_has_tag.xml +++ b/man/udev_device_has_tag.xml @@ -21,9 +21,11 @@ udev_device_has_tag + udev_device_has_current_tag udev_device_get_devlinks_list_entry udev_device_get_properties_list_entry udev_device_get_tags_list_entry + udev_device_get_current_tags_list_entry udev_device_get_sysattr_list_entry udev_device_get_property_value udev_device_get_sysattr_value @@ -36,6 +38,18 @@ #include <libudev.h> + + int udev_device_has_tag + struct udev_device *udev_device + const char *tag + + + + int udev_device_has_current_tag + struct udev_device *udev_device + const char *tag + + struct udev_list_entry *udev_device_get_devlinks_list_entry struct udev_device *udev_device @@ -51,6 +65,11 @@ struct udev_device *udev_device + + struct udev_list_entry *udev_device_get_current_tags_list_entry + struct udev_device *udev_device + + struct udev_list_entry *udev_device_get_sysattr_list_entry struct udev_device *udev_device @@ -62,12 +81,6 @@ const char *key - - int udev_device_has_tag - struct udev_device *udev_device - const char *tag - - const char *udev_device_get_sysattr_value struct udev_device *udev_device @@ -84,22 +97,40 @@ - + udev_device_has_tag() returns a valuer larger than zero if the specified + device object has the indicated tag assigned to it, and zero otherwise. See + udev7 for details on + the tags concept. udev_device_has_current_tag() executes a similar check, however + only determines whether the indicated tag was set as result of the most recent event seen for the + device. Tags are "sticky", i.e. once set for a device they remain on the device until the device is + unplugged, even if the rules run for later events of the same device do not set them anymore. Any tag for + which udev_device_has_current_tag() returns true will hence also return true when + passed to udev_device_has_tag(), but the opposite might not be true, in case a tag is + no longer configured by the rules applied to the most recent device even. + + udev_device_get_tags_list_entry() returns a a + udev_list_entry object, encapsulating a list of tags set for the specified + device. Similar, udev_device_get_current_tags_list_entry() returns a list of tags + set for the specified device as effect of the most recent device event seen (see above for details on the + difference). + Return Value - On success, - udev_device_get_devlinks_list_entry(), + On success, udev_device_has_tag() and + udev_device_has_current_tag() return positive or 0, depending + on whether the device has the given tag or not. On failure, a negative error code is returned. + + On success, udev_device_get_devlinks_list_entry(), udev_device_get_properties_list_entry(), - udev_device_get_tags_list_entry() and - udev_device_get_sysattr_list_entry() return - a pointer to the first entry of the retrieved list. If that list - is empty, or if an error occurred, NULL is + udev_device_get_tags_list_entry(), + udev_device_get_current_tags_list_entry() and + udev_device_get_sysattr_list_entry() return a pointer to the first entry of the + retrieved list. If that list is empty, or if an error occurred, NULL is returned. On success, @@ -119,17 +150,13 @@ contain NUL bytes should not be set with this function; instead, write them directly to the files within the device's syspath. - - On success, udev_device_has_tag() - returns 1 or 0, - depending on whether the device has the given tag or not. - On failure, a negative error code is returned. See Also + udev7, udev_new3, udev_device_new_from_syspath3, udev_device_get_syspath3,