Gábor Csárdi

Never mind, wrong issue...

This boils down to ```r file_info("autoloop", follow = TRUE) ``` This is what the standard Unix tools do and we could do the same. ``` ❯ realpath autoloop realpath: autoloop:...

Based on https://man7.org/linux/man-pages/man7/path_resolution.7.html the limit is 40 for modern Linux kernels.

Not really a rig issue, but rather an issue with R, I would say. It remembers where sed was when it was built, and then it looks for it there...

No worries, it is useful to know that more than one person has the same issue. :D

The other thing that I don't understand is how people end up without `/usr/bin/sed`. It must be an Ubuntu thing, yet on a minimal container it is already there: ```...

@statnmap @eliocamp @nevermana-landcare (from https://github.com/r-lib/ps/issues/110) do you have any clue how your Ubuntu did not have `sed` at both `/bin/sed` and `/usr/bin/sed`? Did you originally update from an earlier version...

Aha, on 18.04 there is no `/usr/bin/sed`, so that could be an explanation for some of the issues. We'll try to work around this in rig.

I think this is already fixed in the latest version of rig, what version are you using?

I would rather fall back to `libconnection.dylib` if the first option was not found, instead of pattern matching.