Description of problem:
If chkconfig is used to set up a TCL based daemon when the PC boots, some of the
children processes created by the daemon will fail with "child process exited
abnormally". The same TCL daemon works fine when started up by crond. This is my
current workaround, namely to have chkconfig default the daemon off at startup
time and let crond start the daemon a minute later. 

Version-Release number of selected component (if applicable):
FC5 2.6.15-1.2054_FC5, TCL 8.4.13

How reproducible:
On demand by the TCL daeamon.

Steps to Reproduce:
1. I will send you the TCL daemon and documentation for you to setup when you
are ready to look at the issue.
2.
3.
  
Actual results:
In general terms, the TCL daemon listens on a selected port. Incoming commands
are passed to the OS for execution. In this case, the daemon takes the following
commands {#!/bin/csh} {setenv DISPLAY :0.0} {setenv XAUTHORITY ~/.Xauthority}
{xhost +localhost}, writes them to a temporay file, makes it executable, then
does "su - root -c /root/scripts/multi_ws_slave_daemon_temp_4.sh" and gets the
error "child process exited abnormally".

Expected results:
The same sequence works fine, with no errors, if crond is the one to start the
TCL daemon.

Additional info:
This issue occurs on both my Fedora Core 5 machines. One is an AMD 1.8Ghz HP
laptop model ze2315us. The other machine is an Intel Pentium 3 800Mhz with an
ASUS motherboard.

This issue does not happen with on the same machines when they are booted with
Red Hat 9 or Solaris 10.