At 09:39 PM 8/17/2004, you wrote: >I'm having a problem with cron in this new environment. I cannot execute any of my >own scripts in my ~/bin. I was also having problems executing even things in /tmp! So >like a good little boy I decided to read the readme for cron again before asking >here. Trouble is I have no cron readme! > >I remember it was in /usr/doc/Cygwin but alas:
Cygwin docs should now be in /usr/share/doc/Cygwin. All packages are moving that direction. >$ ls /usr/doc/cygwin >ctags-5.5.README* openssl-0.9.7d.README* whois-4.6.14-1.README* >ghostscript-7.05.README* procps-010801.README* >mc-4.6.0.README* rxvt-2.7.10.README* > >So I figured "Oops, guess I didn't install all the documentation" and fired up >setup.exe to download from the internet. I use ftp://planetmirror.com and when I >attempt to do that I get: > >(null) line 1537: parse error, unexpected COMMA, expecting STRING >(null) line 1537: unrecognized line 1537 (do you have the latest setup?) >(null) line 1537: unrecognized line 1537 (do you have the latest setup?) >(null) line 1537: unrecognized line 1537 (do you have the latest setup?) > >Problem is I *do* have the latest version of setup! I just downloaded it again to >make sure. Same error. Tried mirrors.kernel.org - same error! I assume you've seen <http://cygwin.com/ml/cygwin/2004-08/msg00587.html> by now. If not, read through it. The problem is fixed. >As for my cron problem I can execute rudimentary commands such as ls, pwd and >redirect the output to /tmp/debug.log. From that I can see that pwd tells me that I'm >in /var/cron. The script I want to execute is under ~/bin (which is on a network >share). I copied that script to /tmp and insured that it was set 777. Then I >performed the following cron jobs: > >18 17 * * * pwd >> /tmp/debug.log 2>&1 >19 17 * * * ls >> /tmp/debug.log 2>&1 >20 17 * * * ls -l /tmp/myscript >> /tmp/debug.log 2>&1 >21 17 * * * /tmp/myscript >> /tmp/debug.log 2>&1 > >Here's the result: > >/var/cron >tabs >-rwxrwxrwx 1 TPAD3741 Domain U 5201 Aug 17 17:15 /tmp/myscript > >/tmp/myscript never get's executed. Sorry, can't really help here. There's just not enough information about what your script does or what your environment for me to hazard a guess. If you post more details or, better yet, a small test case, I can try it. The simple test I did which just echos "Hello World" from a bash script worked fine for me. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
