This one probably relates somewhat to the conversation we're having in
SERVER-1634 about whether we should document the "start" and "stop" subcommands as being for troubleshooting / development purposes only and encourage users to only use the service framework start/stop commands instead.
That said, I think this is one that we "could" do by adding something like the following to the Java command line in the start subcommand:
I'm inclined, though, to think that we shouldn't do this. One issue is that we only use the "daemon" log on pre-systemd systems. For systemd, stderr / stdout from the Java process today is redirected to the journal. If we were to put work into the start script to pipe the output to a log file, we might end up with three different locations that users would have to monitor for their log output on systemd systems - journal, daemon log, and service log. This would seem like a regression to me.
Rob Braden, Melissa Stone, Chris Price - would be interested in your thoughts on this one.