Post Asa4fMLtvnb3RfIska by Suiseiseki@freesoftwareextremist.com
 (DIR) More posts by Suiseiseki@freesoftwareextremist.com
 (DIR) Post #Asa4OA2CTWRIJrt62q by bugaevc@floss.social
       2025-03-28T15:18:40Z
       
       1 likes, 0 repeats
       
       $ pldd 9345593455:/usr/bin/sshdlinux-vdso.so.1/lib64/libcrypto.so.3/lib64/libz.so.1/lib64/libc.so.6/lib64/ld-linux-x86-64.so.2look ma, no libsystemd, no libxz (and yet Type=notify).
       
 (DIR) Post #Asa4fMLtvnb3RfIska by Suiseiseki@freesoftwareextremist.com
       2025-03-30T12:58:05.914557Z
       
       0 likes, 0 repeats
       
       @bugaevc Yes, systemd is often a worse implementation of what already existed somehow.
       
 (DIR) Post #Asa4h7bFkdduGqKBJQ by mr64bit@p.mr64.net
       2025-03-30T12:58:21.883727Z
       
       0 likes, 0 repeats
       
       @bugaevc huh, TIL `pldd`. one of those things I'd never think to look for instead of just `grep \.so /proc/pid/maps`
       
 (DIR) Post #Asa5LgMJw94DepgGhs by bugaevc@floss.social
       2025-03-30T13:03:50Z
       
       1 likes, 0 repeats
       
       @mr64bit yeah, it's relatively little known. grepping/proc/pid/maps will usually produce  a similar result indeed, but the big difference is pldd looks at the actual link map in the processes memory, i.e. glibc loader's (in that process) actual idea of which libraries are loaded (and for what sonames), as opposed to asking the kernel for the complete list of mmapped files and picking out the ones that look like shared libraries.