./executable: cannot execute binary file
I have a script that works well when I ssh to the server to execute it myself, but has problems when Hudson, a continuous integration server, runs it.
bash
Execute bash commands over SSH while staying in interactive mode afterwards
Probably it is a weird thing I would like to achieve but:
I would like to SSH to a remote host and then execute some bash commands like “alias” automatically to use them afterwards in an interactive mode. The remote host does not allow the personal environment.
Fast way to build a test file with every second listed in YYYY-mm-dd HH:MM:SS format
I want to create a large test file with lines containg dates listed by the second, but my method is taking inordinately long… (or at least, that’s how it feels 🙂 … 43 minutes to create only 1051201 lines. 20.1 MB file….
Echoing progress from a background process without hijacking prompt
Consider the simple script hello:
number of folders in a directory (recursive)
I would like to print the number of folders (recursive, excluding hidden folders) in a given CWD / current directory. What command, or series of commands can I use to ascertain this information?
Differentiating between running and being sourced in a bash shell script?
Either what I’m asking here is extremely unorthodox/unconventional/risky, or my Google-fu skills just aren’t up to snuff…
Is there any way to undo a bash history modification?
By pressing up, I can go through previously entered commands. I’ve noticed though that if I modify one of them, that alters the history. For instance, if I type:
Remote for-loop over SSH
I have the following in a script
What is the right way to consistently mangle bash terminal?
I’m on OSX 10.11.1 and occasionally my bash terminal gets mangled. It often happens when I accidentally cat a binary file. The result can be seen on the image below. The output becomes weird, and I can’t type ascii characters anymore.
What are the environment variables by default?
When starting a bash shell process, what are the default environment variables, except those specified in the startup file?