- give people (advanced users, i guess) a workaround if they have ever encountered this problem.
- ask why it is like this...
Simplest way for you to see it for your self is to run: (notice that there is no output until it exits)
Code: Select all
./ManiaPlanetServer /nodaemon | cat
`cat` is a stupid use case, but you could for instance pipe it to a log service, like loggly.
Why do I want to run it without TTY?
- pipe - some log services (eg, loggly) have clients you can pipe to to send to them. `./ManiaPlanetServer /nodaemon | loggly-pipe` - or use `awk` to format the lines differently before writing to disk - many possibilities
- child_process in node.js - running a server as child_process under node.js, and getting a stream of the console could allow for some cool ideas for GSP's.
- docker.io - magic
Code: Select all
script -qc "./ManiaPlanetServer /nodaemon" /dev/null | cat
To summarize:
What is the reason for not flushing output when not in a TTY context?
And if people has had this issue, and haven't found a workaround. Well... now you have a workaround. (took me a long time to find it)