Background processes don't generally send output to the console, because they are not associated with a console. If you just want to see if it's running:
ps -x | egrep 'MyProcessName' If you want to temporarily bring a background process to the foreground, use the "fg" bash builtin. As Chris said, processes can be written to handle signals and some common programs (like Apache) will spit out some status info if you send them a USR1 signal, like: kill -s USR1 processID Just try it and see what happens. You could also send the output to an unused console window, like /dev/tty10 and then just switch to the window when you want to see what it's doing. (That may require some aditional setup in your inittab, though.) Ron Smith ----------- On Thu, 6 Feb 2014 14:34:34 -0500 Curt Howland <howl...@priss.com> wrote: > Good afternoon. > > I have a background process running from which I would like, from time > to time, to check the console output. I do not want to dedicate a > console window to it, and since I start it from a script the console > output is usually just lost to the akashic ethers. > > I've not played with fifo buffers, but I'm wondering. Could I start > the process with " > fifo-buffer.txt" and then when I want to check > the output, run a "tail -f fifo-buffer.txt" for a few minutes? > > Since this is not a usual background process with log rotation and > such, I don't want to fill my disk with a text file dump. But it would > be nice to check in and make sure it's running without killing it and > restarting. > > Suggestions? > > -- > The secret of happiness is freedom, > and the secret of freedom is courage. > - Thucydides > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
