Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Not every Linux system has /dev/fd

Open
#517 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux

Research direction

Start in src/posix/close_handles.cpp around line 181 and trace how Boost.Process discovers file descriptors when /dev/fd is unavailable. The change is complete when /proc/self/fd is tried as a fallback on affected Linux systems and the existing project tests still pass.

Written by the indexing model from the issue text.

Description

I have found a couple of embedded Linux devices old enough to not have close_range, and that happen to lack the /dev/fd -> /proc/self/fd symlink (AFAICT it's not required by POSIX either). They do have /proc/self/fd, though.

So it would be nice if Boost.Process would try also in /proc/self/fd if /dev/fd fails: https://github.com/boostorg/process/blob/1bfe21baa32acc64f865c65ef5924b167de33439/src/posix/close_handles.cpp#L181

Dominant language
C++
Stars
145
Forks
151
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/process

All issues in boostorg/process

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.