I have an embedded ARM device running Linux which launches an application on boot. This application has a bunch of
"printf(...)" statements in it that I need to view. The normal way I have been approaching this is to kill the running app through SSH (from a host PC) on the embedded device after it boots, and then re-launch it via the SSH terminal so that I can see the print statements in the console on the host PC. The problem with this is that the app does not behave well after killing and re-launching it.
What I have attempted to do is edit the startup script to say
"(nohup ./myAppName 2>&1 | logger) &" and view
tail -f.. however, nothing is getting logged.
I have verified that
"(nohup echo "test123" 2>&1 | logger) &" does indeed log properly to the syslog.
Where might things be going wrong? Is it possible that the app is not printing to stdout/stderr? When I do relaunch the app, it does properly print to the console, but like I said, other things beyond the scope of this are broken when I do so.