/dev/fd errors on freebsd

[wlcx]

Fresh install of latest homeshick, on freebsd 10

$ ~/.homesick/repos/homeshick/bin/homeshick refresh
/home/samw/.homesick/repos/homeshick/bin/homeshick: line 111: /dev/fd/62: No such file or directory
/home/samw/.homesick/repos/homeshick/lib/fs.sh: line 21: /dev/fd/62: No such file or directory
/home/samw/.homesick/repos/homeshick/lib/fs.sh: line 21: /dev/fd/61: No such file or directory

[andsens]

what the f...? I've never seen an error like that before. Is it something you can reproduce reliably? Try using the interactive testing tool as described in the guidelines.

My best guess with the limited info here is that you've run out of file descriptors, since it's a fresh install however, there shouldn't be anything that could hog that many FDs (except if you have a backup tool installed that monitors file changes).

[wlcx]

Right, so having made shebang modifications (https://github.com/wlcx/homeshick/tree/development, not sure if you want me to PRQ that) I have tried test/interactive, and the same issue is present.

$ homeshick clone wlcx/dotfiles
        clone https://github.com/wlcx/dotfiles.git
      updates The castle dotfiles has new files.
     symlink? [yN] y
/tmp/tmp.N5QPEvme/home/.homesick/repos/homeshick/lib/commands/link.sh: line 3: /dev/fd/62: No such file or directory
$ /tmp/tmp.N5QPEvme/home/.homesick/repos/homeshick/lib/commands/link.sh: line 78: /dev/fd/62: No such file or directory
/tmp/tmp.N5QPEvme/home/.homesick/repos/homeshick/lib/commands/link.sh: line 78: /dev/fd/61: No such file or directory

Clone runs fine, link/refresh/list etc all cause an FD error. Also, I noticed that the command exits (as evidenced by the $) before the latter two errors. Wierd. I have tried on two separate freebsd systems, incidentally.

[andsens]

Right, so having made shebang modifications

The shebangs are really just there for syntax highlighting purposes, only bin/homeshick needs the proper /usr/bin/env bash.... and lib/submodule_files.sh, which it doesn't - that could definitely cause problems, I'll fix that.

[wlcx]

On current development HEAD, I get:
$ $HOME/.homesick/repos/homeshick/test/interactive /home/samw/.homesick/repos/homeshick/test/interactive: /home/samw/.homesick/repos/homeshick/test/setup-default.sh: /bin/bash: bad interpreter: No such file or directory
Which is why I changed all of them :p something of a blunt approach I realise.

[andsens]

I have pushed a possible fix to the development branch. Could you check it out and see if it works?

p.s.: If you could post a short script that reproduces the error in interactive mode, I will make a regression test for it so it doesn't happen again.

[andsens]

OK, so the line numbers all closely correspond to pieces of code that use process substitution (which actually makes sense).

Could you try executing find -L "$repos" -mindepth 2 -maxdepth 2 -name .git -type d -print0 | sort -z ($repos being $HOME/.homesick/repos) and post the output?

[wlcx]

Current development still errors:

$ homeshick link dotfiles
/home/samw/.homesick/repos/homeshick/lib/commands/link.sh: line 3: /dev/fd/62: No such file or directory
/home/samw/.homesick/repos/homeshick/lib/commands/link.sh: line 78: /dev/fd/62: No such file or directory
/home/samw/.homesick/repos/homeshick/lib/commands/link.sh: line 78: /dev/fd/61: No such file or directory

Find output:

$ find -L "$repos" -mindepth 2 -maxdepth 2 -name .git -type d -print0 | sort -z
/home/samw/.homesick/repos/dotfiles/.git/home/samw/.homesick/repos/homeshick/.git

[dougborg]

This is most likely a bug in FreeBSD or a configuration issue on those environments (bash version, udev, etc.). I do not have much experience with FreeBSD, but it looks like people run into this issue on other projects:

https://github.com/sstephenson/rbenv/wiki
rbenv/rbenv#401
http://www.ducea.com/2009/02/18/linux-tips-bash-completion-devfd62-no-such-file-or-directory/

It could also have to do with how homeshick is being invoked:
http://unix.stackexchange.com/questions/124838/process-substitution-from-curl-to-bash-as-root

[dougborg]

This might be a good fix candidate to try out: rbenv/rbenv#401 (comment)

[wlcx]

Oho. sudo mount -t fdescfs fdesc /dev/fd and now things are fixed.
@gavinatkinson, who knows more than I ever will, pointed out that bash now requires fdescfs(5) mounted on /dev/fd which FreeBSD does not yet do as default.

[andsens]

Yay! Thank you for reporting back the fix! Could you add the fix to the FAQ? I created it just now for that purpose and I think other people could really use the pointer when running FreeBSD.