[hotani]

I'd like to find a gentle way to do this without manually looking up the process and killing it. I need something that can go in a script. "stop" does not seem to work, and there is nothing in the options that would do this.

[Turias]

Originally posted by hotani:
I'd like to find a gentle way to do this without manually looking up the process and killing it. I need something that can go in a script. "stop" does not seem to work, and there is nothing in the options that would do this.

Are you going through the terminal? You could just leave that window open and use CTRL-C to quit whenever you like.

If you really want to run it in the background, you can probably write a shell script that finds the correct process number and kills it (and then even write an applescript wrapper around that shell script). Maybe mikkyo or another of the shell-writing masters on this board can help you with that one.

[hotani]

yeah, I have it running in the background - it starts up with the machine via shell script. However, I'd like to kill it while gaming since although it shouldn't interfere, it does (i've got the benchmarks to prove it! ).

i thought about writing something to find the process id and kill it, but was wondering if there was a nicer way to do it.

[Turias]

Originally posted by hotani:
i thought about writing something to find the process id and kill it, but was wondering if there was a nicer way to do it.

I don't think there is. dFold has a cool thing they do in which they create a lock file on application start. If that file gets deleted, they cleanly shut down. This makes it really easy to stop the app whenever you like. It's too bad F@H doesn't do something similar.

[hotani]

got it:

'killall FahCore_78.exe'

not pretty, but it works.

[Turias]

Originally posted by hotani:
got it:

'killall FahCore_78.exe'

not pretty, but it works.

That only works with that core. You might be running a different core depending on the protein.

[hotani]

hmmmm - good point. There is just one other core in the directory _65.exe, if I put both in the script it will just ignore the one not running... unless of course its creating more of these .exe files.