On Tuesday, March 03, 1998 8:51 PM, Bill Studenmund 
[SMTP:skippy@macro.stanford.edu] wrote:

>
> Someone tracked this problem down to something to do w/ job control when
> xfs starts. Something like "set -E" before and "set +E" after (or was it
> "+E" and "-E"?) the xfs command in the rc script was the magic
> incantation...
>
> Take care,
>
> Bill

On Tuesday, March 03, 1998 8:05 PM, Jonathan Stone 
[SMTP:jonathan@DSG.Stanford.EDU] wrote:

>
> Doing "unset -m" (or "set -m"?)  in /etc/rc turned off (or turned on?)
> job control.  This supposedly fixed the race and fixed the symptoms
> with xfs on a pmax hanging on its first connection from an Xserver.
>

Between Jonathan and Bill I managed to find a solution.  Adding a "set -m" 
prior to the xfs command in /etc/rc avoids the race condition.  It didn't 
seem to make any difference whether I had a "set +m" after the xfs command 
or not.  I opted to leave it out.  The man page indicates that the "set -m" 
shell command does the following:

-m	monitor
	Turn on job control (set automatically when interactive).

If someone knows whether or not I should be turning job control back off 
after the xfs command please let me know.  Thanks for the help guys,

Rob Mohr