Log through a FIFO, then redirect to a file?

view full story

http://serverfault.com – I have an application that must log each transaction. Every log message is flushed because we need to have a record of what occurred leading up to a crash. My colleagues and I were curious about how to achieve the performance effects of buffering while guaranteeing that the log message had left the process. What we came-up with is: make a FIFO that the application can write to, and redirect the contents of that FIFO to a regular file via cat. Are there any gotchas to this approach? It worked when we tested it, but we want to make absolutely sure that the messages will find their way to th (HowTos)