Glenn, Thanks for the thought.... I have tried using 'sleep 15' after a call to load each application. Didnt seem to help at all. /root/gsg/bin/start_server user1 sleep 15 /root/gsg/bin/start_server user2 sleep 15 etc.... I looked at the boot.log and it seems it starts all the applications, but completes only 8 out of 11 (on one server). The 'boot.log' file indicates that the application processes are overlapping - the log has entries for one application finishing after another started, etc. So, maybe I will increase the sleep to 45 seconds? Luke > Are you using any variation of the sleep command? I've got an > ancient, > slow processor and wanting some apps to start up along with boot, I > issued the sleep command on each app to stagger the load and demand > so > that my old worn out processor could manage. > > luke@xxxxxxxxxxxxx wrote: > >> Getting this script to run on boot is not a >>problem so far..... >>the problem is that the script only gets to 3 or 4 of the users >>applications on boot. I can run this script manually, so I know its >>not a permission issue. >>Im guessing that loading all 7 of these applications is either >>taking too long or using too many resources - or both. > This was my problem. and after adding the sleep command for a few 'ms' > to the different apps, everything worked great. > >>After doing >>some reading Im wondering if the 'batch' or 'at' commands might >> help >>to alleviate any load issues on boot and allow all 7 applications >> to >>start every time the server does..... > Don't know about having to go and do that, but I do know that > staggering > the load and demand priorities of each app allowed a relatively > quick > and smooth startup. > > -Glenn- > - : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
