LISTSERV - FMPRO-L Archives - LISTSERV.DARTMOUTH.EDU

FMPRO-L Archives

January 2011, Week 5

FMPRO-L@LISTSERV.DARTMOUTH.EDU

	LISTSERV Archives
	FMPRO-L Home
	FMPRO-L January 2011, Week 5

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

Options:	Use Monospaced Font Show Text Part by Default Show All Mail Headers
Message:	[<< First] [< Prev] [Next >] [Last >>]
Topic:	[<< First] [< Prev] [Next >] [Last >>]
Author:	[<< First] [< Prev] [Next >] [Last >>]

Subject:	Re: Why can't I use "killall"
From:	Corn Walker <[log in to unmask]>
Reply To:	FileMaker Pro Discussions <[log in to unmask]>
Date:	Mon, 31 Jan 2011 21:29:42 -0500
Content-Type:	text/plain
Parts/Attachments:	text/plain (15 lines)

On Jan 31, 2011, at 9:08 PM, Peter Payne wrote:

> Question for smarter Mac-heads than me. I can quit apps using "killall" via scripting the terminal, for example if Transmit has frozen I can use "killall transmit" to kill and relaunch it. (I do this in scripts that run in the background, to make sure the scripts are running overnight.) However, no force in the universe will make Filemaker Pro die with "killall." Any idea what I would need to do? Any variation of "killall 'Filemaker Pro'" or "killall 'Filemaker Pro.app'" returns "no matching processes belonging to you were found." Is there some magic trick to this?

The correct syntax is "killall FileMaker\ Pro"

Why are you killing FileMaker via the Terminal?

-corn


Cornelius Walker
The Proof Group
http://proofgroup.com/

ATOM RSS1 RSS2

LISTSERV.DARTMOUTH.EDU