Page MenuHomeFreeBSD always use absolute path for syscalls.conf

Authored by brooks on May 30 2019, 8:34 PM.



syscalls.conf is included using "." which per the Open Group:

If file does not contain a <slash>, the shell shall use the search path
specified by PATH to find the directory containing file.

POSIX shells don't fall back to the current working directory.

Submitted by: Nathaniel Wesley Filardo <>

Diff Detail

Lint OK
No Unit Test Coverage
Build Status
Buildable 24610
Build 23393: arc lint + arc unit

Event Timeline

brooks created this revision.May 30 2019, 8:34 PM
bdrewery requested changes to this revision.May 30 2019, 8:43 PM
bdrewery added inline comments.

Please use ${.CURDIR} instead of ./ in all of this. That will churn less with my change which does that.

This revision now requires changes to proceed.May 30 2019, 8:43 PM
brooks updated this revision to Diff 58093.May 30 2019, 8:47 PM
  • Use ${.CURDIR} instead of ".".
bdrewery accepted this revision.May 30 2019, 8:50 PM
This revision is now accepted and ready to land.May 30 2019, 8:50 PM
brooks retitled this revision from always use relative path for syscalls.conf to always use absolute path for syscalls.conf.May 30 2019, 8:54 PM
This revision was automatically updated to reflect the committed changes.