| | 324 | === Scheduler debugging === |
| | 325 | <scheduler_log_buffer>N</scheduler_log_buffer>:: |
| | 326 | Set the output buffer of the scheduler log to N bytes. |
| | 327 | Set it to zero to see all msgs before a crash. |
| | 328 | |
| | 329 | <debug_req_reply_dir>path</debug_req_reply_dir>:: |
| | 330 | If specified, each scheduler instance will write three |
| | 331 | files in there: PID_C_sched.log, PID_C_sched_request.xml and (if all |
| | 332 | goes well) PID_C_sched_reply.xml. PID is the process id of this |
| | 333 | scheduler instance, C is an internal counter within the process if |
| | 334 | FCGI is used. The sched.log will contain nothing else than the |
| | 335 | pid and the IP address of the client. This should allow for |
| | 336 | identifying the scheduler instance responsible for a given |
| | 337 | apache error log message ("premature end of script headers") when |
| | 338 | a scheduler crashed. sched_request.xml (obviously) is the scheduler |
| | 339 | request, and if the scheduler doesn't crash in between, there will |
| | 340 | also be the reply to the client kept in sched_reply.xml |
| | 341 | |
