* [QnA] procfs: How to read the unresolved location of an executable?
@ 2025-09-19 16:21 Martin Rodriguez Reboredo
0 siblings, 0 replies; only message in thread
From: Martin Rodriguez Reboredo @ 2025-09-19 16:21 UTC (permalink / raw)
To: Linux filesystem development
I have an MWE with a combined multi utils executable like BusyBox. I know I
can use the arguments passed to deduct which name the executable was invoked
with.
$ ln -s multi example
$ ./example # example should show in argv
I want to do the same with procfs but if I use `/proc/self/exe` it points out
to the full path of multi instead of example's. Is there a way to know the
location of example with procfs? My intention is to use this location with
frameworks like Electron to find resource paths relative to the one of the
invoking executable.
Your answers are thanked in advance.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-09-19 16:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-09-19 16:21 [QnA] procfs: How to read the unresolved location of an executable? Martin Rodriguez Reboredo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).