EOF is not a character nor an "event" and could not be sent through the pipe, or "fed" to its writing end, as some stubborn urban legend suggests.
The only way to generate an
EOF on the reading end of a pipe/fifo (ie cause a
read(2) on it to return 0) is to close all open handles to its writing end.
This will happen automatically if all the processes that had opened a named pipe in write mode and all the children that have inherited the file descriptors through
fork() are terminated .
It's not possible for a
read(2) on a named pipe to return 0 it that pipe was opened in read/write mode, eg. with
because in that case there is a single file descriptor / handle for both ends of the pipe and closing the write end will also close the read end making impossible for a
read(2) to return 0 (pipes do not support any kind of half-close as sockets do with
 And all processes that have received the file descriptor via
SCM_RIGHTS ancillary message on a unix socket.
tail -f by definition won't terminate upon
EOF, whether the file it's reading from is regular or special. One way to kill all processes that are holding a open handle to a file descriptor is with
tail -f /path/to/fifo
> /path/to/fifo # let any blocking open(2) through
fuser -TERM -k /path/to/fifo
Beware that this will also kill processes that have (inadvertently) inherited an open handle to
/path/to/fifo from their parents.