| 10 | | file would be a pipe even though it appears not to be one, ie. |
| 11 | | we have blocking access to that file until the other end of the |
| 12 | | pipe in the host file system actually writes data to it which |
| 13 | | unblocks the guest access to that file again, ie. the behavior |
| 14 | | of an ordinary pipe. |
| | 8 | file would be a named pipe/fifo even though it appears not to be one, ie. when reading, we have blocking access to that file until the other end of the named pipe /fifo in the host file system actually writes data to it which unblocks the guest access to that file again, ie. the behavior of an ordinary named pipe/fifo. |
| 16 | | 4) although 3) appears to be the pipe behavior it is actually not |
| 17 | | really. once the host end of the pipe has written something into |
| 18 | | the pipe special file, the guest unblocks but fails with an |
| 19 | | error "Protocol error" and no actual data did travel from the |
| 20 | | host pipe end to the guest pipe end. |
| | 10 | 4) although 3) appears to be the named pipe behavior it is actually not really. once the hosts sending end of the named pipe/fifo has written something into the named pipe/fifo special file, the guest unblocks but fails with an error "Protocol error" and no actual data did travel from the hosts |
| | 11 | named pipe sending end to the guest named pipe receiving end. |
| 23 | | regular/pipe file blocks until there is a reader on the |
| 24 | | other end of this pipe in the host side. Once there is a reader |
| 25 | | at the host end of the pipe, the guests writing process unblocks, |
| 26 | | ie. like in 3) we sort of have the behavior of an ordinary pipe. |
| | 14 | "regular|/named pipe file blocks until there is a reader on the |
| | 15 | other end of this named pipe in the host side. Once there is a reader at the host end of the named pipe/fifo, the guests writing process unblocks,ie. like in 3) we sort of have the behavior of an ordinary named pipe/fifo. |
| 34 | | 7) when a process in the guest reads or writes to that file |
| 35 | | in the shared folder file system that is supposed to be a pipe |
| 36 | | special file (from the hosts perspective at least), you cannot |
| 37 | | interrupt this process with CTRL+C or by a signal, eg. kill -15, |
| 38 | | anymore when there is no process on the other (host) side end |
| 39 | | of the pipe. That behavior is not the case for process on the |
| 40 | | regular file system. |
| | 19 | 7) when a process in the guest reads or writes to that file |
| | 20 | in the shared folder file system that is supposed to be a named pipe/fifo special file (from the hosts perspective at least), you cannot interrupt this process with CTRL+C or by a signal, eg. kill -15, anymore when there is no process on the other (host) side end of the named pipe/fifo. That behavior is not the case for process doing the same in the regular file system. |