Closed GoogleCodeExporter closed 8 years ago
Gaetan,
the command you're using won't actually do anything visible. Part of the
problem is that I chose such a bad default command :) Try using:
/usr/bin/open /Applications/TextEdit.app
That should open TextEdit when the task triggers.
Hope that helps,
Sven
Original comment by sven.a.s...@gmail.com
on 7 Oct 2010 at 11:14
Hi Sven
I have tried that but it doesnt work.
Please advise if possible
Kind regards
Gaetan.
Original comment by gaetanba...@gmail.com
on 7 Oct 2010 at 12:17
Attachments:
I see TextEdit is open in your Dock. I'm not sure if you'd notice the script
being triggered in that case. Best try to run the command from the command line
first to see how/if it's working. That way it's easier to tell if it's working.
You could also touch a file on the file system "/usr/bin/touch <path to file>"
and check the time stamp. That way you don't have to schedule a single event
but could schedule it with "*" in all fields and see if the file gets touched
every minute. Hope that helps.
PS: You could check if your cron daemon is actually running:
ps aux | grep cron
This should list a process "cron" (along with the grep command possibly)
Original comment by sven.a.s...@gmail.com
on 7 Oct 2010 at 12:28
Hi
I have closed the textedit and tried to run it again but it didnt work. Sorry
to be pain but I am more a pc man I have asked someone who knows a bit more
about macs to how to run things from the command.
Kind regards
Gaetan.
Original comment by gaetanba...@gmail.com
on 7 Oct 2010 at 2:26
Attachments:
No worries :) In a nutshell: open the application "Terminal" (inside
Applications/Utilities) and type or copy-paste the commands I've listed, i.e.:
/usr/bin/open /Applications/TextEdit.app
and
ps aux | grep cron
This is the unix command line. Cron, the underlying tool, is really a unix tool
and CronniX just a front-end for its configuration. It's pretty unixy down
there so if you're looking for a GUI automation tool, CronniX may not be your
best choice to be honest :) I'm not trying to scare you off and there are ways
to use cron to schedule GUI stuff of course (for example via AppleScript) but
there's a learning curve to it, unfortunately.
Cheers,
Sven
Original comment by sven.a.s...@gmail.com
on 7 Oct 2010 at 2:38
Hi Sven
This really good service.
It failed on the first command and passed on the second one.
Original comment by gaetanba...@gmail.com
on 7 Oct 2010 at 3:23
Attachments:
Well, actually, both failed ;) The first command is actually wrong the way you
entered it, it's:
/usr/bin/open /Applications/TextEdit.app
Note the blank after open. We're using the 'open' command (full path given) to
open the app TextEdit.app inside Applications.
Now the second command tells me that the cron daemon is not running on your OSX
system. I'm not sure why that is or how it could have happened. cron is running
by default on 10.4. Best try power cycling the machine and see if cron comes
up. Use the command to check, it should look similar to this:
% ps aux | grep cron
sas 88785 0.6 0.0 2435040 532 s002 R+ 6:31PM 0:00.00 grep cron
root 44 0.0 0.0 2435968 416 ?? Ss 25Sep10 0:01.00
/usr/sbin/cron
Without cron showing up here, no tasks will be triggered.
HTH,
Sven
Original comment by sven.a.s...@gmail.com
on 7 Oct 2010 at 4:32
Hi Sven
I have rebooted the server and done the command test to open the text
application again, it worked this time but the second test failed.
Kind regards
Gaetan
Original comment by gaetanba...@gmail.com
on 8 Oct 2010 at 7:56
Attachments:
Gaetan,
the '%' was my prompt. The command starts with just 'ps'.
-sas
Original comment by sven.a.s...@gmail.com
on 8 Oct 2010 at 8:01
Hi Sven
Sorry about that, I didnt know as my prompt is different.
Original comment by gaetanba...@gmail.com
on 8 Oct 2010 at 8:08
I forgot to attached the file.
Original comment by gaetanba...@gmail.com
on 8 Oct 2010 at 8:09
Attachments:
Ok, you don't have a cron daemon running for some reason. It should be up by
default on 10.4. I'm afraid you're going to have to have some admin look into
this, something seems to be wrong with your box.
-sas
Original comment by sven.a.s...@gmail.com
on 8 Oct 2010 at 8:17
Thanks for all your help anyway.
Kindest regards
Gaetan.
Original comment by gaetanba...@gmail.com
on 8 Oct 2010 at 8:23
Original comment by sven.a.s...@gmail.com
on 3 Nov 2010 at 10:44
Original issue reported on code.google.com by
gaetanba...@gmail.com
on 7 Oct 2010 at 10:43Attachments: