LaunchAgent to quit Safari

I have the following launchagent:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>jte.safari</string>
<key>ProgramArguments</key>
<array>
<string>/usr/bin/osascript</string>
<string>-e</string>
<string>"tell application \"Safari\" to quit"</string>
</array>
<key>ServiceDescription</key>
<string>Quit Safari</string>
<key>StartCalendarInterval</key>
<dict>
<key>Hour</key>
<integer>6</integer>
<key>Minute</key>
<integer>15</integer>
</dict>
</dict>
</plist>

Which should quit Safari every morning at 6:15, only it doesn't. I
checked today and the safari process was a month old.

I have other LaunchAgents that work fine. It is loaded and listed as
active in `launchctl list | grep jte.safari`

Generally the machine is asleep at 6:15, but my understanding was that a
timed event would fire the next time it could, not simply be skipped.

Any ideas?

--
I WILL NOT DO THE DIRTY BIRD Bart chalkboard Ep. AABF08

Lewis <> wrote:
> I have the following launchagent:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
> "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
> <plist version="1.0">
> <dict>
> <key>Label</key>
> <string>jte.safari</string>
> <key>ProgramArguments</key>
> <array>
> <string>/usr/bin/osascript</string>
> <string>-e</string>
> <string>"tell application \"Safari\" to quit"</string>
> </array>
> <key>ServiceDescription</key>
> <string>Quit Safari</string>
> <key>StartCalendarInterval</key>
> <dict>
> <key>Hour</key>
> <integer>6</integer>
> <key>Minute</key>
> <integer>15</integer>
> </dict>
> </dict>
> </plist>
>
> Which should quit Safari every morning at 6:15, only it doesn't. I
> checked today and the safari process was a month old.
>
> I have other LaunchAgents that work fine. It is loaded and listed as
> active in `launchctl list | grep jte.safari`
>
> Generally the machine is asleep at 6:15, but my understanding was that a
> timed event would fire the next time it could, not simply be skipped.
>
> Any ideas?


Perhaps try a shell command instead of an AppleScript?
> killall Safari

should do the trick

In message <188686924364650244.906733thom.rosario->
Thom Rosario <> wrote:
> Lewis <> wrote:
>> I have the following launchagent:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
>> "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
>> <plist version="1.0">
>> <dict>
>> <key>Label</key>
>> <string>jte.safari</string>
>> <key>ProgramArguments</key>
>> <array>
>> <string>/usr/bin/osascript</string>
>> <string>-e</string>
>> <string>"tell application \"Safari\" to quit"</string>
>> </array>
>> <key>ServiceDescription</key>
>> <string>Quit Safari</string>
>> <key>StartCalendarInterval</key>
>> <dict>
>> <key>Hour</key>
>> <integer>6</integer>
>> <key>Minute</key>
>> <integer>15</integer>
>> </dict>
>> </dict>
>> </plist>
>>
>> Which should quit Safari every morning at 6:15, only it doesn't. I
>> checked today and the safari process was a month old.
>>
>> I have other LaunchAgents that work fine. It is loaded and listed as
>> active in `launchctl list | grep jte.safari`
>>
>> Generally the machine is asleep at 6:15, but my understanding was that a
>> timed event would fire the next time it could, not simply be skipped.
>>
>> Any ideas?


> Perhaps try a shell command instead of an AppleScript?
>> killall Safari

The point is to have this fire at 06:15 every single day, or as soon as
the machine wakes up in the morning if it's after 06:15.

The osascript command works, it is the LaunchAgent that doesn't seem to work.

--
THE PRESIDENT DID IT IS NOT AN EXCUSE Bart chalkboard Ep. AABF05

In message <jollyroger->
Jolly Roger <> wrote:
> In article <>,
> Lewis <> wrote:

>> I have the following launchagent:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
>> "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
>> <plist version="1.0">
>> <dict>
>> <key>Label</key>
>> <string>jte.safari</string>
>> <key>ProgramArguments</key>
>> <array>
>> <string>/usr/bin/osascript</string>
>> <string>-e</string>
>> <string>"tell application \"Safari\" to quit"</string>
>> </array>
>> <key>ServiceDescription</key>
>> <string>Quit Safari</string>
>> <key>StartCalendarInterval</key>
>> <dict>
>> <key>Hour</key>
>> <integer>6</integer>
>> <key>Minute</key>
>> <integer>15</integer>
>> </dict>
>> </dict>
>> </plist>
>>
>> Which should quit Safari every morning at 6:15, only it doesn't. I
>> checked today and the safari process was a month old.
>>
>> I have other LaunchAgents that work fine. It is loaded and listed as
>> active in `launchctl list | grep jte.safari`
>>
>> Generally the machine is asleep at 6:15, but my understanding was that a
>> timed event would fire the next time it could, not simply be skipped.
>>
>> Any ideas?

> Have you examined the system log to see if there are entries around the
> time the event is supposed to happen?

Yes, and there's nothing at all in them. The user is not an admin user, so he doesn't have access to all the loggin, so I will try and reload the LaunchAgent and doublecheck if the admin account sees anything in the logs.

--
When we woke up that morning we had no way of knowing that in a matter
of hours we'd changed the way we were going. Where would I be now? Where
would I be now if we'd never met? Would I be singing this song to
someone else instead?

In message <jollyroger->
Jolly Roger <> wrote:
> BTW, if Safari is not running, your script will cause it to launch. ; )

Launch and then quit. Small price to pay for getting it to quit on a
regular basis. I have never seen it take multiple GB of real memory on
my machines, but on this one last time I checked it was using 10.4GB of
Real Memory for something like 8 tabs.

--
Just give us a kiss to celebrate here, today.

In message <nibvd9->
Paul Sture <> wrote:
> Why not put the whole call to osascript into a script and call that?

I will probably do that.

--
Mirrors contain infinity. Infinity contains more things than you think.
Everything, for a start. Including hunger. Because there's a million
billion images, but only one soul to go around. --Witches Abroad

On Wed, 18 Jul 2012 02:49:25 -0400, Lewis wrote
(in article <>):

> I have the following launchagent:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
> "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
> <plist version="1.0">
> <dict>
> <key>Label</key>
> <string>jte.safari</string>
> <key>ProgramArguments</key>
> <array>
> <string>/usr/bin/osascript</string>
> <string>-e</string>
> <string>"tell application \"Safari\" to quit"</string>
> </array>
> <key>ServiceDescription</key>
> <string>Quit Safari</string>
> <key>StartCalendarInterval</key>
> <dict>
> <key>Hour</key>
> <integer>6</integer>
> <key>Minute</key>
> <integer>15</integer>
> </dict>
> </dict>
> </plist>
>
> Which should quit Safari every morning at 6:15, only it doesn't. I
> checked today and the safari process was a month old.
>
> I have other LaunchAgents that work fine. It is loaded and listed as
> active in `launchctl list | grep jte.safari`
>
> Generally the machine is asleep at 6:15, but my understanding was that a
> timed event would fire the next time it could, not simply be skipped.
>
> Any ideas?

You're missing the username argument:

right before the last </dict> add:

<key>UserName</key>
<string>your short user name here</string>
</dict>
</plist>

In message <Z0gPr.9781$%>
John Drako <> wrote:
> On Wed, 18 Jul 2012 02:49:25 -0400, Lewis wrote
> (in article <>):

>> I have the following launchagent:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
>> "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
>> <plist version="1.0">
>> <dict>
>> <key>Label</key>
>> <string>jte.safari</string>
>> <key>ProgramArguments</key>
>> <array>
>> <string>/usr/bin/osascript</string>
>> <string>-e</string>
>> <string>"tell application \"Safari\" to quit"</string>
>> </array>
>> <key>ServiceDescription</key>
>> <string>Quit Safari</string>
>> <key>StartCalendarInterval</key>
>> <dict>
>> <key>Hour</key>
>> <integer>6</integer>
>> <key>Minute</key>
>> <integer>15</integer>
>> </dict>
>> </dict>
>> </plist>
>>
>> Which should quit Safari every morning at 6:15, only it doesn't. I
>> checked today and the safari process was a month old.
>>
>> I have other LaunchAgents that work fine. It is loaded and listed as
>> active in `launchctl list | grep jte.safari`
>>
>> Generally the machine is asleep at 6:15, but my understanding was that a
>> timed event would fire the next time it could, not simply be skipped.
>>
>> Any ideas?

> You're missing the username argument:

> right before the last </dict> add:

> <key>UserName</key>
> <string>your short user name here</string>
> </dict>
> </plist>

I have well more than a dozen ~/Library/LaunchAgents and not one has a
Username key. As I understand it, the username is only used if you want
a task to run from /Library as a specific user instead of either root
(LaunchDaemons) or the user logging in (LaunchAgents).

--
what was supposed to be so special about a full moon? It was only a big
circle of light. And the dark of the moon was only darkness. But
half-way between the two, when the moon was between the worlds of light
and dark, when even the moon lived on the edge... maybe then a witch
could believe in the moon. --Witches Abroad

On Mon, 23 Jul 2012 22:47:26 -0400, Lewis wrote
(in article <>):

> In message <Z0gPr.9781$%>
> John Drako <> wrote:
>> On Wed, 18 Jul 2012 02:49:25 -0400, Lewis wrote
>> (in article <>):
>
>>> I have the following launchagent:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
>>> "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
>>> <plist version="1.0">
>>> <dict>
>>> <key>Label</key>
>>> <string>jte.safari</string>
>>> <key>ProgramArguments</key>
>>> <array>
>>> <string>/usr/bin/osascript</string>
>>> <string>-e</string>
>>> <string>"tell application \"Safari\" to quit"</string>
>>> </array>
>>> <key>ServiceDescription</key>
>>> <string>Quit Safari</string>
>>> <key>StartCalendarInterval</key>
>>> <dict>
>>> <key>Hour</key>
>>> <integer>6</integer>
>>> <key>Minute</key>
>>> <integer>15</integer>
>>> </dict>
>>> </dict>
>>> </plist>
>>>
>>> Which should quit Safari every morning at 6:15, only it doesn't. I
>>> checked today and the safari process was a month old.
>>>
>>> I have other LaunchAgents that work fine. It is loaded and listed as
>>> active in `launchctl list | grep jte.safari`
>>>
>>> Generally the machine is asleep at 6:15, but my understanding was that a
>>> timed event would fire the next time it could, not simply be skipped.
>>>
>>> Any ideas?
>
>> You're missing the username argument:
>
>> right before the last </dict> add:
>
>> <key>UserName</key>
>> <string>your short user name here</string>
>> </dict>
>> </plist>
>
> I have well more than a dozen ~/Library/LaunchAgents and not one has a
> Username key. As I understand it, the username is only used if you want
> a task to run from /Library as a specific user instead of either root
> (LaunchDaemons) or the user logging in (LaunchAgents).

It helped in the past for me. Give it a try before dismissing it.

In article <t8pPr.94645$ >,
John Drako <> wrote:

> On Mon, 23 Jul 2012 22:47:26 -0400, Lewis wrote
> (in article <>):
>
> > In message <Z0gPr.9781$%>
> > John Drako <> wrote:
> >> On Wed, 18 Jul 2012 02:49:25 -0400, Lewis wrote
> >> (in article <>):
> >
> >>> I have the following launchagent:
> >>>
> >>> <?xml version="1.0" encoding="UTF-8"?>
> >>> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
> >>> "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
> >>> <plist version="1.0">
> >>> <dict>
> >>> <key>Label</key>
> >>> <string>jte.safari</string>
> >>> <key>ProgramArguments</key>
> >>> <array>
> >>> <string>/usr/bin/osascript</string>
> >>> <string>-e</string>
> >>> <string>"tell application \"Safari\" to quit"</string>
> >>> </array>
> >>> <key>ServiceDescription</key>
> >>> <string>Quit Safari</string>
> >>> <key>StartCalendarInterval</key>
> >>> <dict>
> >>> <key>Hour</key>
> >>> <integer>6</integer>
> >>> <key>Minute</key>
> >>> <integer>15</integer>
> >>> </dict>
> >>> </dict>
> >>> </plist>
> >>>
> >>> Which should quit Safari every morning at 6:15, only it doesn't. I
> >>> checked today and the safari process was a month old.
> >>>
> >>> I have other LaunchAgents that work fine. It is loaded and listed as
> >>> active in `launchctl list | grep jte.safari`
> >>>
> >>> Generally the machine is asleep at 6:15, but my understanding was that a
> >>> timed event would fire the next time it could, not simply be skipped.
> >>>
> >>> Any ideas?
> >
> >> You're missing the username argument:
> >
> >> right before the last </dict> add:
> >
> >> <key>UserName</key>
> >> <string>your short user name here</string>
> >> </dict>
> >> </plist>
> >
> > I have well more than a dozen ~/Library/LaunchAgents and not one has a
> > Username key. As I understand it, the username is only used if you want
> > a task to run from /Library as a specific user instead of either root
> > (LaunchDaemons) or the user logging in (LaunchAgents).
>
> It helped in the past for me. Give it a try before dismissing it.

While it obviously can't hurt to try, I think he's right. UserName
isn't needed in personal LaunchAgent files, only in the system-wide
file. I've never had to add that in any of my LaunchAgent files.

In fact, I'd go so far as to say that putting it in personal files would
be *wrong*. User A shouldn't be able to run programs as User B, so what
would be the point if the only name you can put there is the one that it
knows it has to run the program as.

I suspect the problem is the quoting. Try changing:

<string>"tell application \"Safari\" to quit"</string>

to:

<string>tell application "Safari" to quit</string>

Quotes around a string are only needed for the shell, but LaunchDaemon
is running the program directly, not going through a shell. And the
separate <string>...</string> elements in the array already indicate
that it's a single string argument.

--
Barry Margolin,
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***