From 2ea24611b99d12955ba374f072148b9ad6d644dc Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Mon, 27 Mar 2023 18:16:40 +0200 Subject: pid1: add DumpFileDescriptorStore() bus call that returns fdstore content info --- man/org.freedesktop.systemd1.xml | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) (limited to 'man/org.freedesktop.systemd1.xml') diff --git a/man/org.freedesktop.systemd1.xml b/man/org.freedesktop.systemd1.xml index ab94a90b7c..1a82a19bbd 100644 --- a/man/org.freedesktop.systemd1.xml +++ b/man/org.freedesktop.systemd1.xml @@ -273,6 +273,8 @@ node /org/freedesktop/systemd1 { LookupDynamicUserByUID(in u uid, out s name); GetDynamicUsers(out a(us) users); + DumpUnitFileDescriptorStore(in s name, + out a(suuutuusu) entries); signals: UnitNew(s id, o unit); @@ -974,6 +976,8 @@ node /org/freedesktop/systemd1 { + + @@ -1531,6 +1535,11 @@ node /org/freedesktop/systemd1 { New Control Group Interface for more information how to make use of this functionality for resource control purposes. + + DumpUnitFileDescriptorStore() returns an array with information about the + file descriptors currently in the file descriptor store of the specified unit. This call is equivalent + to DumpFileDescriptorStore() on the + org.freedesktop.systemd1.Service. For further details, see below. @@ -2548,6 +2557,7 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice { in b read_only, in b mkdir, in a(ss) options); + DumpFileDescriptorStore(out a(suuutuusu) entries); GetProcesses(out a(sus) processes); AttachProcesses(in s subcgroup, in au pids); @@ -3742,6 +3752,8 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice { + + @@ -4393,6 +4405,16 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice { directly on the Manager object has the advantage of not requiring a GetUnit() call to get the unit object for a specific unit name. Calling the methods on the Manager object is hence a round trip optimization. + + DumpFileDescriptorStore() returns an array with information about the file + descriptors currently in the file descriptor store of the service. Each entry consists of a file + descriptor name (i.e. the FDNAME= field), the file descriptor inode type and access + mode as integer (i.e. a mode_t value, flags such as S_IFREG, + S_IRUSR, …), the major and minor numbers of the device number of the file system + backing the inode of the file descriptor, the inode number, the major and minor numbers of the device + number if this refers to a character or block device node, a file system path pointing to the inode, + and the file descriptor flags (i.e. O_RDWR, O_RDONLY, + …). -- cgit v1.2.1