Timeline for View console output from an Upstart job without logfiles
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:36 | history | edited | CommunityBot |
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
|
|
| Aug 19, 2016 at 3:29 | history | edited | Nick | CC BY-SA 3.0 |
adding more detail to the question and desired outcome
|
| Aug 19, 2016 at 0:21 | answer | added | Timo | timeline score: 0 | |
| Aug 18, 2016 at 22:18 | answer | added | user147505 | timeline score: 0 | |
| Aug 18, 2016 at 21:48 | history | edited | Gilles 'SO- stop being evil' | CC BY-SA 3.0 |
edited tags
|
| Aug 18, 2016 at 21:39 | history | edited | Nick | CC BY-SA 3.0 |
added more research
|
| Aug 18, 2016 at 21:36 | comment | added | Nick | @ryekayo- i appreciate your indirect suggestion. log4j is an enormous PIA, especially with its newer version and the conflicting documentation. In a more direct answer, its because this is how it is written today, and I need a fast way to connect to it, rather than rewriting my app. Maybe one day I will. | |
| Aug 18, 2016 at 20:00 | comment | added | ryekayo | Why arent you using log4j or one of Java's libraries for logging? These types of libraries will log output to a txt or log file that you can tail. A system.out.println statement will NOT write to a log file.. | |
| Aug 18, 2016 at 19:55 | history | asked | Nick | CC BY-SA 3.0 |