piped

Those two articles don’t talk much about what kind of structure/format the records getting piped around have.

That would catch all the people who `curl | less` first and then run it again piped to bash).

They can be scripted and piped, and an admin worth his salt could easily find the info he needs with them.

The solution to the problem was to start a new thread that kept reading the piped stdout and move it to another buffer.

That's probably one of the reasons PowerShell was designed to execute the commands in-process: The objects being piped are just the object references.

My software is most easily installed with a piped bash script.

This is how, for example, many Unix programs detect whether they're being piped into another program and to therefore be more strict about their output.

I would have piped this through awk, but this is probably better done with macros.

Say I have a command that I want to read both a piped in stdin _and_ interactive input from the user.

(1) It was a different person every time, and (2) all booking is done online, with SMS interactions piped through Twilio.

Another web request piped into an interpreter.

Then I piped that into less, just to be grumpy.

Also, because expect(1) defeats the entire "remote shell" aspect of SSH, which lets me do this from my workstation: ssh server tar zc /srv/http > http-backup.tar.gz Yes, that's a remote command whose output is piped to a local file.

The author writes "this is for people who aren't 'devops' and who can't crank out a fancy piped shell script using awk and sed." Whatever we may feel about people who have inexplicably failed to learn to use awk or sed, or perl, or python, or ruby, criticism on the basis of these methods being "better" (if only one learns how to use them) is a waste of everyone's time.