No server.out log file

[davidadale]

I am using the plugin to package an application. The problem I am having is that it seems to want to create a server.out log file. I really don't need this file. Is there a way of telling the script not to create a server.out file?

[jjlauer]

Hi @davidadale - not sure if this is still an issue for you, but v2.6.0 is out and I spent some time cleaning this up and some of the new features may help you. If you are using SystemV inits (e.g. Ubuntu 14.04) than nohup is used to make your java process a daemon. In this case stdout has to go somewhere. While we could add a feature to let you route it to something like /dev/null -- if you run into an issue starting your app, you will have a difficult time troubleshooting it.

Originally, stork's systemd support just tapped into the same logic. v2.6.0 changes how SystemD is used by default. Since SystemD doesn't require nohup, the latest launchers from Stork now use exec if SystemD is being used. This doesn't touch your stdout streams and no file will be generated. However, please note that stdout still routes somewhere and by default systemd will usually log that data to journald.

For own use of Stork, we usually log our apps to both stdout and log files, but we now detach logging to stdout in our own app once we know it started correctly. That way we can see the errors in systemd (e.g. systemctl status <name>), but then if the app starts simply log everything to the log file.