I think I had a line running every minute, something alike
echo "cron is running" > /Macintosh\ HD/Users/admin/testcron.txt
as echo is a built-in I didn't think I'd have to add the path to it,
and I feel I still don't understand it fully:
a quick look at
man builtin
shows:
Thus, while
specifying ``echo'' causes a builtin command to be executed under shells
that support the builtin echo command, specifying ``/bin/echo'' or
``./echo'' does not.
Does that mean I need to set a shell environment table
(SHELL=/bin/bash - as described in man 5 crontab), before cron can
execute built-ins?
I have it running for my needs, but still I'd be glad if you could
help me understand this matter.
Some shells have the echo command built into them. Other shells don't
and need to use the echo program. If the latter then you need to say
which echo you're using and where it is.
If you require a shell that has echo built in then you either need to
define the $SHELL in the crontab (poor idea), execute the shell as
part of the command in the crontab entry (better, clearer) or invoke
command.
--
-dhan
------------------------------------------------------------------------
Dan Shoop AIM: iWiring
Systems & Networks Architect http://www.ustsvs.com/
email@hidden http://www.iwiring.net/
1-714-363-1174
"The wise man doesn't give the right answers, he poses the right
questions." -- Claude Levi-Strauss
iWiring provides systems and networks support for Mac OS X, unix, and
Open Source application technologies at affordable rates.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
