At the end of a nohup command add "/dev/null &" instead of just "&". This will eliminate the creation of the nohup.out file.
As to Q2, size of detail.log file:
The solution implemented by most customers I've seen is to regularly rename the existing file and create a new detail.log . At least under Unix/Linux/Windows this works fine because the file is not kept open all the time but only whenever new messages shall be saved there.
I've seen cron jobs (running a short shell script) and batch files (simply renaming the existing file and creating a new one) to perform this task on a regular basis.
BTW you better post such questions on the PowerExchange forum (not PowerExchange Adapters!), there you will find the right experts.
Moving thread to PowerExchange community.
In addition to Leroy and Nico's responses, you might want to consider using Alternative Logging.
When you add a TRACING statement to DBMOVER.CFG, anything run using that DBMOVER.CFG will use Alternative Logging.
This routes the messaging from each component to its own message log file, and provides options to control the size of such files, and the number of files to keep before "wrapping" and overwriting the previous message log files.
It can also make troubleshooting easier, as each component's messages are isolated.
With Alternative Logging, the only things that go to detail.log is some of the initialization messages.
1. For Condense file size below two parameters you can change:
2. Please find some examples showing the setup.
You can add below statements in dbmover file whcih you use to start listener and logger and create the appropiate files.
and then recycle Listener and logger.
Listener log will be created at location ABC\PowerExchange**\BCD\Altlogs\DTLLST*
Logger log will be created at location ABC\PowerExchange**\BCD\Altlogs\Pwxccl*
and also you can control the size of the logs using TRACING parameter settings SIZE.
3. Script, you can test on linux machine, where you are running, the requirement is to run the process from Power Exchange home directory. If you use LOGPATH and Tracing then logs should be created as above.
You can read more about these statements in Power Exchange Reference Manual.