I had planned on putting in a signal handler whereby I could:
'kill -USR1 pid'
and have it spit the information out to the terminal. The problem is, if I run the program in the background and log out, it has no associated terminal to output to when I log back in. As a result, any print statements go straight to the bit bucket as far as I can tell. Is there any way to do this in a reasonably sane manner?
In reply to Diagnositc output on background processes by gomez18
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |