X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsd_pid_get_session.xml;h=a8266e02062f222bff09a9f9e7d0637f678fa876;hp=9a1b1997d96ac3da5a82f6d1f0d9f35ffd1ac16e;hb=05a2f6fefedd7254fd799502191d025d2908cf74;hpb=5430f7f2bc7330f3088b894166bf3524a067e3d8;ds=sidebyside
diff --git a/man/sd_pid_get_session.xml b/man/sd_pid_get_session.xml
index 9a1b1997d..a8266e020 100644
--- a/man/sd_pid_get_session.xml
+++ b/man/sd_pid_get_session.xml
@@ -21,7 +21,7 @@
along with systemd; If not, see .
-->
-
+
sd_pid_get_session
@@ -45,8 +45,19 @@
sd_pid_get_session
sd_pid_get_unit
+ sd_pid_get_user_unit
sd_pid_get_owner_uid
- Determine session, service or owner of a session of a specific PID
+ sd_pid_get_machine_name
+ sd_pid_get_slice
+ sd_peer_get_session
+ sd_peer_get_unit
+ sd_peer_get_user_unit
+ sd_peer_get_owner_uid
+ sd_peer_get_machine_name
+ sd_peer_get_slice
+ Determine session, service, owner of a
+ session, container/VM or slice of a specific
+ PID or socket peer
@@ -65,11 +76,65 @@
char** unit
+
+ int sd_pid_get_user_unit
+ pid_t pid
+ char** unit
+
+
int sd_pid_get_owner_uid
pid_t pid
uid_t* uid
+
+
+ int sd_pid_get_machine_name
+ pid_t pid
+ char** name
+
+
+
+ int sd_pid_get_slice
+ pid_t pid
+ char** slice
+
+
+
+ int sd_peer_get_session
+ int fd
+ char** session
+
+
+
+ int sd_peer_get_unit
+ int fd
+ char** unit
+
+
+
+ int sd_peer_get_user_unit
+ int fd
+ char** unit
+
+
+
+ int sd_peer_get_owner_uid
+ int fd
+ uid_t* uid
+
+
+
+ int sd_peer_get_machine_name
+ int fd
+ char** name
+
+
+
+ int sd_peer_get_slice
+ int fd
+ char** slice
+
@@ -91,18 +156,28 @@
call after use.
sd_pid_get_unit() may be
- used to determine the systemd unit (i.e. system
+ used to determine the systemd system unit (i.e. system
service) identifier of a process identified by the
- specified process identifier. The unit name is a short
- string, suitable for usage in file system paths. Note
- that not all processes are part of a unit/service
+ specified PID. The unit name is a short string,
+ suitable for usage in file system paths. Note that not
+ all processes are part of a system unit/service
(e.g. user processes, or kernel threads). For
- processes not being part of a systemd unit/system
- service this function will fail. The returned string
- needs to be freed with the libc
+ processes not being part of a systemd system unit this
+ function will fail. (More specifically: this call will
+ not work for processes that are part of user units,
+ use sd_pid_get_user_unit() for
+ that.) The returned string needs to be freed with the
+ libc
free3
call after use.
+ sd_pid_get_user_unit() may
+ be used to determine the systemd user unit (i.e. user
+ service) identifier of a process identified by the
+ specified PID. This is similar to
+ sd_pid_get_unit() but applies to
+ user units instead of system units.
+
sd_pid_get_owner_uid() may
be used to determine the Unix user identifier of the
owner of the session of a process identified the
@@ -114,15 +189,42 @@
and not being a shared process of a user this function
will fail.
- If the pid paramater of any
- of these functions is passed as 0 the operation is
+ sd_pid_get_machine_name()
+ may be used to determine the name of the VM or
+ container is a member of. The machine name is a short
+ string, suitable for usage in file system paths. The
+ returned string needs to be freed with the libc
+ free3
+ call after use.
+
+ sd_pid_get_slice() may be
+ used to determine the slice unit the process is a
+ member of. See
+ systemd.slice5
+ for details about slices. The returned string needs to
+ be freed with the libc
+ free3
+ call after use.
+
+ If the pid parameter of any
+ of these functions is passed as 0, the operation is
executed for the calling process.
+
+ The sd_peer_get_session(),
+ sd_peer_get_unit(),
+ sd_peer_get_user_unit(),
+ sd_peer_get_owner_uid(),
+ sd_peer_get_machine_name() and
+ sd_peer_get_slice() calls operate
+ similar to their PID counterparts, but operate on a
+ connected AF_UNIX socket and retrieve information
+ about the connected peer process.
Return Value
- On success these calls return 0 or a positive
+ On success, these calls return 0 or a positive
integer. On failure, these calls return a negative
errno-style error code.
@@ -131,12 +233,20 @@
Notes
The sd_pid_get_session(),
- sd_pid_get_pid(), and
- sd_pid_get_owner_uid() interfaces
- are available as shared library, which can be compiled
+ sd_pid_get_unit(),
+ sd_pid_get_user_unit(),
+ sd_pid_get_owner_uid(),
+ sd_pid_get_machine_name(),
+ sd_pid_get_slice(),
+ sd_peer_get_session(),
+ sd_peer_get_unit(),
+ sd_peer_get_user_unit(),
+ sd_peer_get_owner_uid(),
+ sd_peer_get_machine_name() and
+ sd_peer_get_slice() interfaces are
+ available as a shared library, which can be compiled
and linked to with the
- libsystemd-login
- pkg-config1
+ libsystemd pkg-config1
file.
Note that the login session identifier as
@@ -151,9 +261,10 @@
systemd1,
- sd-login7,
+ sd-login3,
sd_session_is_active3,
- getsid2
+ getsid2,
+ systemd.slice5