Skip to main content
Post Undeleted by animuson
Post Unlocked by animuson
Post Locked by CommunityBot
Post Deleted by muru, CommunityBot
added 45 characters in body
Source Link
Arcticooling
  • 4.5k
  • 18
  • 56
  • 107

How does a FIFO (named pipe) differs from a regular pipe (|)? As I understand from Wikipedia, unlike a regular pipe, a FIFO pipe "keeps living" after the process has ended and can be deleted sometime afterwards.

But if f the process is based on a shell command containing a pipe (cat x | grep y), we could "keep it alive after the process" if we store it in a variable or a file, isn't it then a FIFO?

Also, a regular pipe also has the first stdout it gets, as stdin for another commandfirst stdout it gets, as stdin for another command, so isn't it also a kind of first in first out pipe as well?

How does a FIFO (named pipe) differs from a regular pipe (|)? As I understand from Wikipedia, unlike a regular pipe, a FIFO pipe "keeps living" after the process has ended and can be deleted sometime afterwards.

But if f the process is based on a shell command containing a pipe (cat x | grep y), we could "keep it alive after the process" if we store it in a variable or a file, isn't it then a FIFO?

Also, a regular pipe also has the first stdout it gets, as stdin for another command, so isn't it also a kind of first in first out pipe?

How does a FIFO (named pipe) differs from a regular pipe (|)? As I understand from Wikipedia, unlike a regular pipe, a FIFO pipe "keeps living" after the process has ended and can be deleted sometime afterwards.

But if f the process is based on a shell command containing a pipe (cat x | grep y), we could "keep it alive after the process" if we store it in a variable or a file, isn't it then a FIFO?

Also, a regular pipe also has the first stdout it gets, as stdin for another command, so isn't it also a kind of first in first out pipe as well?

Tweeted twitter.com/StackUnix/status/983864679280861184
edited title
Link
Arcticooling
  • 4.5k
  • 18
  • 56
  • 107

How does a FIFO (named pipe) differs from a regular pipe (|unnamed pipe)?

deleted 183 characters in body
Source Link
Arcticooling
  • 4.5k
  • 18
  • 56
  • 107

How does a FIFO (named pipe) differs from a regular pipe (|)?

  As I understand from Wikipedia this, unlike a regular pipe, a FIFO pipe "keeps living" after the process washas ended and can be deleted sometime afterwards.

I don't understand what is the meaning of keep living after a process - I can't think of regular pipes in that way, I'll explain:

IfBut if f the process is based on a shell command containing a pipe (cat x | grep y), we can just writecould "keep it again (or, expandalive after the process" if we store it fromin a variable). If the process is based on running or a file with a script with 1 or more commands, wellisn't it then a FIFO?

Also, the code is already ina regular pipe also has the filefirst stdout it gets, as stdin for another command, so what is the meaning of keep being alive after the process was ended that I cannot imagine forisn't it also a regular pipekind of first in a commandfirst out pipe?

How does a FIFO (named pipe) differs from a regular pipe (|)?

  As I understand from Wikipedia this pipe "keeps living" after the process was ended and can be deleted sometime afterwards.

I don't understand what is the meaning of keep living after a process - I can't think of regular pipes in that way, I'll explain:

If the process is based on a shell command containing a pipe (cat x | grep y), we can just write it again (or, expand it from a variable). If the process is based on running a file with a script with 1 or more commands, well, the code is already in the file, so what is the meaning of keep being alive after the process was ended that I cannot imagine for a regular pipe in a command?

How does a FIFO (named pipe) differs from a regular pipe (|)? As I understand from Wikipedia, unlike a regular pipe, a FIFO pipe "keeps living" after the process has ended and can be deleted sometime afterwards.

But if f the process is based on a shell command containing a pipe (cat x | grep y), we could "keep it alive after the process" if we store it in a variable or a file, isn't it then a FIFO?

Also, a regular pipe also has the first stdout it gets, as stdin for another command, so isn't it also a kind of first in first out pipe?

added 157 characters in body
Source Link
Arcticooling
  • 4.5k
  • 18
  • 56
  • 107
Loading
Source Link
Arcticooling
  • 4.5k
  • 18
  • 56
  • 107
Loading