You're dealing with two output channels, stdout
. The system automatically opens three channels for you, stdin
(the keyboard, channel 0), stdout
(the monitor, channel 1) and stderr
(the monitor, channel 2). You can redirect channel 1 and channel 2; i.e., when you
that puts standard output into file
. When you do
that puts standard error into /dev/null
, the system black hole. By the same token, you can redirect standard error into one file and standard output into another file:
prog > file01 2> file02
Or (in you case you don't care about this) you can combine standard output and standard error into one
Now the above a valid for sh
(the Bourne based shells) -- if you're using C-Shell, well, that last time I used that was about 30 years ago and I've forgotten how to do redirects with it (it's different), sorry.
If you just execute your program (without nohup
) do you get double logs? If so, it might be a good idea to actually specify log files in the program -- open, write to, close -- to avoid duplication (or, maybe, tell JBoss to shut up, eh?). If that's not a problem, try the above and see what you get.
Hope this helps some.