News for hackers. Stuff that matters.
Re:Understanding the bin, sbin, usr/bin, usr/sbin split (2010) by criddell on Wednesday May 11, 2022 @10:46AM (#31340712)
Is that ever going to be a hot path?
Re:Understanding the bin, sbin, usr/bin, usr/sbin split (2010) by naniwaduni on Wednesday May 11, 2022 @02:30PM (#31343946)
It's probably not exactly going to be hot, but even failing execve is inherently semi-expensive since it needs to be a syscall and incurs context switches.

It's just outweighed a couple orders of magnitude by all the overhead that comes with a successfully launching another executable unless you have, like, a thousand junk paths in your PATH.

Re:Understanding the bin, sbin, usr/bin, usr/sbin split (2010) by hnlmorg on Wednesday May 11, 2022 @01:10PM (#31342867)
Theoretically can be. Every command you invoke without a path will need to look up PATH.

In practice well behaving shells cache the contents of PATH to speed up operations.