Can you help a n00b out here? I put the processing in the background and explicitly called exit.
#!/bin/sh /Applications/Firefox3.app/Contents/MacOS/firefox-bin -no-remote -P dev & exit Still holding up my QS. I'm just finding the script and using the 'run' action, so that may be my problem. Thanks. On Oct 28, 5:57 pm, "Jon Stovell (a.k.a. Sesquipedalian)" <[EMAIL PROTECTED]> wrote: > If you were to run thescriptusing Terminal, you would find that the > Terminal window would appear to freeze until you closed it. When you > closed it you would discover that in so doing you had quit running thescript. > This is all because Terminal would be the app that actually > executed thescript. So it wouldn't be frozen, it would just be doing > what it was told. > > QS works the same way as Terminal in this regard. If theshellscript > is designed to keep running until forced to quit, then QS will keep > running it, and thus be busy with that and unavailable to do other > things. > > Instead, try writing ascriptthat (1) starts the mainscriptas a > separate process, and then (2) quits itself. Add this startupscript > to QS instead of the mainscript. > > On Oct 28, 1:54 am, mmcduff <[EMAIL PROTECTED]> wrote: > > > I have ashellscript(to run synergy - a keyboard/mouse sharing over > > TCP program), which I've added to the catalog. Theshellscript > > should continue running until I run anotherscriptto kill it. The > > problem is that running the start-upscriptcauses Quicksilver to > > freeze. Any ideas?
