It is not conflicting in any way. The "detached" option if checked causes 24x7 to start another instance of 24x7 to run the job and then exit. This way, the job runs our of the first process space and does not affect the stability. This is what the "detached" option is for. The use of the combination "asynchronous" and "detached" may lead to almost duplicate entries in the job log. One entry is written by the spawned instance indicating the actual job completion. The other entry is written by the main instance indicating that the spawned instance completion. This is because in the "asynchronous" run mode the main instance has to monitor the spawned instance as an independent operation system process.
If you want to avoid the duplicate entries run the job in "synchronous" mode. If you have other long running synchronous jobs put your KSH job into a separate job queue to avoid possible delays. : I am fairly new to 24x7 and have noticed that in one particular job we run(
: which is a KSH script and monitors that servers are up) this job displays
: that it has finished twice with identical times. The job runs every 5
: minutes and has the following options checked to run asynchronous and
: detached after it was thought the job was bringing down the 24x7 service
: (almost every 10 minutes). It does seem almost stable now but i am still
: uncertain as to why the two logging times. I also notice from the schedule
: log that the job also starts its own 24x7 session and another 24x7 icon
: appears in the start up programs until the monitoring job has complete. Is
: this conflicting in any way with the first instance of 24x7?
|
