A little background: We are running D3 emulation on linux. D3 is an old pick mainframe that has been ported for modern hardware. The software just runs inside the D3 environment.

The problem is that when D3 starts automatically, quite a few of the printers do NOT work. The only way to make them work is to stop D3 and restart it. When I run D3 by hand, the printers just work. Currently, I am calling D3 from the last line in the rc.local script. This is, of course, being called by S99local in rc3.d.

The question:
Is there a way to make rc.local wait say, 30 seconds after all other commands are processed to start the D3 process? I mean, I could take it out altogether, but in the case of a problem on a week-end, it means D3 will not start properly on its own. My gut feeling is that there's a race-condition with the equinox drivers and D3 is beating the drivers up. Any thoughts?

Another possibility, it appears the equinox drivers are getting started by rc.local as well. Could they safely be moved? I can't figure why not, but I'm no expert.

TIA

Would inserting 'sleep 30s' in the line before work?

Are you serious? I'd kick something if it were that simple. I DID just move the equinox stty setups from rc.local to it's own S92Equinox file, since I'm thinking it's mainly the equinox printers that don't work. I'll have to verify that though. Do those commands wait for the previous command to finish before they kick off? Oh, and since it's a production box, I need to be fairly sure before I reboot the thing to test it.

Wow, I see that sleep command in other sscripts, only no s. just sleep 1 I assume sleeps 1 second. Cool.

In that case, all should be golden. Thanks guys.