If you were to run the script using 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 the script. This is all because Terminal would be the app that actually executed the script. 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 the shell script 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 a script that (1) starts the main script as a separate process, and then (2) quits itself. Add this startup script to QS instead of the main script. On Oct 28, 1:54 am, mmcduff <[EMAIL PROTECTED]> wrote: > I have a shell script (to run synergy - a keyboard/mouse sharing over > TCP program), which I've added to the catalog. The shell script > should continue running until I run another script to kill it. The > problem is that running the start-up script causes Quicksilver to > freeze. Any ideas?
