Is this just a pipe dream?

You are closer than you think.

Have a daemon/service that creates a fifo/named-pipe with the filename you want, and then it can do whatever you want with whatever is written to the "file".

I think that's called 'syslog' on some OSs?

To slightly clarify what BrowserUk said, what you're looking for is already a feature of most operating systems, including pretty much any UNIX-based OS you like. The feature is usually referred to as "named pipes" or "FIFOs".

You use a command mkfifo to create what is basically a dummy entry in the filesystem. You then write your script to read lines from that filename in a loop. When there are no lines to be read, then Perl's readline operator (i.e. <$fh>) will automatically wait until lines are available.

Other processes can then just open that file in write mode and write lines to it, just like it was a normal file. Your script will wake up when lines are available and be able to process them. If your script is slow to process the data then the process writing the data will just act like it's writing to a slow disk. Nothing actually gets written to disk (except the directory entry for the filename); the data streams from the output filehandle of one process to the input handle of the other process.

This is basically just the same technique as chaining together commands in the shell using the pipe (|), but rather than the pipes being anonymous, they have filenames attached to them. Hence "named pipes".

Named pipes are pretty awesome for interprocess communication, though can be fiddly to set up, so generally people use things like TCP sockets instead. The one place where named pipes beat sockets is where (as in your question) either the reader or the writer has not been written with interprocess communication in mind, so you need to "trick" it into thinking it's reading from a plain old file.

I seem to remember at one point using named pipes to include a randomly generated message in my e-mail signatures, when at the time my mail client could only read signatures from a static text file.

perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'

Sounds like a regular virtual filesystem , and would you look at that mount an executable as filesystem -> http://stackoverflow.com/questions/595765/mount-executable-as-file-on-linux-unix-filesystem -> Fuse

I have a bunch of servers that run various proprietary software applications that are only capable of writing logfiles locally, and I don't have access to these remote systems.

My thought was that I would provide the file to someone that has access. They put the file where it needs to be then the data being written to the file would be sent to my server.

At least now I understand what "named pipes" means (I have seen that for years without knowing what they were)