Conversation
Notices
-
@charlie_root
Hey... I have a strange and really dumb situation with bash in arch. I have a script that ran fine a few days ago, but hangs now. It runs fine on debian.
The script hangs if
name=$(find . -type f -iname "$1")
Is in the script, even if not used. It won't run anything after that variable line. It will if I hashtag it.
putting
find . -type f -iname "$1"
By itself runs, but hangs if I pipe it.
all of my arch machines are effected. I had to run it on a debian server and send the ultimate output, a local print command,
back to my cpu over ssh -t (I don't have a printer set up on that server).
Can you think of anything my shell would be missing that would cause a script to hang at those points?
I know there's nothing wrong with it syntactically because it used to work in arch and still does in debian.
-
I assume something got borked by an update. I'm just not sure what needs to be rolled back.
-
@Humpleupagus
Hmmm....
Scripting is not my thing you could maybe ask some tech bros on here. I have a couple to cc, just give me a sec because I have to switch over to a bloat interface.
-
So... I've figured out this much... it has something to do with sshfs.
The first command is to cd into a directory that's fuse mounted.
If I cd to a local directory, the script will exit.
If I cd into the mount and run find, it will also exit.
If find is in a variable and that variable is after the cd into the mount, it hangs.
Find also runs fine at command if I'm in a mount directory, but hangs if I pipe it into e.g. sed. Find..... | sed .... hangs.
🤔