Re: Cron problem/Documentation and Setup
Larry Hall wrote: This doesn't explain why it worked at my last company and why I could have sworn it used to work here up until about a week ago. Well, if you can check the access permissions on the share in question, you should be able to determine whether this is an issue or not. At this company I don't think they'll let me. But assuming I could, what exactly would I look for? IOW what would indicate a public mount and what would indicate a non-public mount? -- Daddy, why doesn't this magnet pick up this floppy disk? -- 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/
Re: Cron problem/Documentation and Setup
At 02:25 AM 8/19/2004, you wrote: Larry Hall wrote: This doesn't explain why it worked at my last company and why I could have sworn it used to work here up until about a week ago. Well, if you can check the access permissions on the share in question, you should be able to determine whether this is an issue or not. At this company I don't think they'll let me. But assuming I could, what exactly would I look for? IOW what would indicate a public mount and what would indicate a non-public mount? See if Everybody or Guest have permissions. Generally speaking, you're looking for ids with access which don't require authentication. For pre-defined groups, this comes down to the two I mentioned. Theoretically, others could be created that fit this definition but limit access to just those within a defined group. I haven't tested the notion. It's just an idea that seems workable. -- 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/
Re: Cron problem/Documentation and Setup
Larry Hall wrote: 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. Ah yes. I knew there was another place to look but all I could remember was /usr/doc. I'll have a look see when I get into work. $ 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. Yes, saw it right after I posted this. Tried a quick download from planetmirror.com again and received the same error. I assumed the fixes was purqulating(sp?) and decided to try again today. Again, once I get into work... 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 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 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. Well initially it was a Perl script that I'm trying to run through cron. But I then stripped it down to just: #!/bin/bash echo testme /tmp/debug.log 21 Nothing additional got written into /tmp/debug.log. -- Diplomacy - the art of letting someone have your way. -- 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/
Re: Cron problem/Documentation and Setup
On Wed, 18 Aug 2004, Andrew DeFaria wrote: Larry Hall wrote: 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! [snip] 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 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 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. Well initially it was a Perl script that I'm trying to run through cron. But I then stripped it down to just: #!/bin/bash echo testme /tmp/debug.log 21 Nothing additional got written into /tmp/debug.log. You have, of course, reviewed Problem reports: http://cygwin.com/problems.html and thought of attaching the output of cygcheck -svr, right? Also, did you try cron_diagnose.sh (Google for it)? I suspect some or all of your mounts may not be visible to cron... Do your cron jobs above (i.e., 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 ) still work correctly after changing ls to /bin/ls? Does changing /tmp/myscript to sh -c '/tmp/myscript' help any? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing. -- Dr. Jubal Harshaw -- 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/
RE: Cron problem/Documentation and Setup
-Original Message- From: cygwin-owner On Behalf Of Igor Pechtchanski Sent: 18 August 2004 16:54 18 17 * * * pwd /tmp/debug.log 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 I haven't been following, so PMFBI, but can I just point out that it may well be necessary that the 21 should precede the /tmp/debug.log if you want stderr to actually end up in the log file BTW, uname -a; pwd; set; export might be a good diagnostic command to add as a cron job isn't this almost certainly a wrong-user-executing-the-job problem? cheers, DaveK -- Can't think of a witty .sigline today -- 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/
RE: Cron problem/Documentation and Setup
On Wed, 18 Aug 2004, Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of Igor Pechtchanski Sent: 18 August 2004 16:54 18 17 * * * pwd /tmp/debug.log 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 I haven't been following, so PMFBI, but can I just point out that it may well be necessary that the 21 should precede the /tmp/debug.log if you want stderr to actually end up in the log file Nope, that part was correct. If you put 21 before the redirection, stderr will end up on stdout. See the sh and bash manpages. BTW, uname -a; pwd; set; export might be a good diagnostic command to add as a cron job isn't this almost certainly a wrong-user-executing-the-job problem? Huh? uname -a should only be useful if there's more than one Cygwin version on the machine -- otherwise, the output should be identical for all users. pwd is already there. I don't see how set;export; is relevant at all, frankly... Did you, by chance, mean id instead? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing. -- Dr. Jubal Harshaw -- 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/
RE: Cron problem/Documentation and Setup
-Original Message- From: Igor Pechtchanski Sent: 18 August 2004 17:19 On Wed, 18 Aug 2004, Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of Igor Pechtchanski Sent: 18 August 2004 16:54 18 17 * * * pwd /tmp/debug.log 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 I haven't been following, so PMFBI, but can I just point out that it may well be necessary that the 21 should precede the /tmp/debug.log if you want stderr to actually end up in the log file Nope, that part was correct. If you put 21 before the redirection, stderr will end up on stdout. See the sh and bash manpages. My bad. GOK how I managed to misremember that, but I was sooo certain that I'd had to painfully discover that they needed to be the other way round myself once. Guess I must have discovered it the way round you've got it, after all. I just tested redirection under cmd.exe and even that behaves the same way, so I didn't even get it from M$-world. Pardon my confabulation. BTW, uname -a; pwd; set; export might be a good diagnostic command to add as a cron job isn't this almost certainly a wrong-user-executing-the-job problem? Huh? uname -a should only be useful if there's more than one Cygwin version on the machine -- otherwise, the output should be identical for all users. pwd is already there. I don't see how set;export; is relevant at all, frankly... Did you, by chance, mean id instead? I meant id rather than uname, yes. As for set; export, I don't see how you can consider the execution environment to _not_ be relevant; it's full of useful and even vital diagnostic information, such as $PATH, to name but one cheers, DaveK -- Can't think of a witty .sigline today -- 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/
RE: Cron problem/Documentation and Setup
On Wed, 18 Aug 2004, Dave Korn wrote: -Original Message- From: Igor Pechtchanski Sent: 18 August 2004 17:19 On Wed, 18 Aug 2004, Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of Igor Pechtchanski Sent: 18 August 2004 16:54 18 17 * * * pwd /tmp/debug.log 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 I haven't been following, so PMFBI, but can I just point out that it may well be necessary that the 21 should precede the /tmp/debug.log if you want stderr to actually end up in the log file Nope, that part was correct. If you put 21 before the redirection, stderr will end up on stdout. See the sh and bash manpages. My bad. GOK how I managed to misremember that, but I was sooo certain that I'd had to painfully discover that they needed to be the other way round myself once. Guess I must have discovered it the way round you've got it, after all. I just tested redirection under cmd.exe and even that behaves the same way, so I didn't even get it from M$-world. Pardon my confabulation. BTW, uname -a; pwd; set; export might be a good diagnostic command to add as a cron job isn't this almost certainly a wrong-user-executing-the-job problem? Huh? uname -a should only be useful if there's more than one Cygwin version on the machine -- otherwise, the output should be identical for all users. pwd is already there. I don't see how set;export; is relevant at all, frankly... Did you, by chance, mean id instead? I meant id rather than uname, yes. As for set; export, I don't see how you can consider the execution environment to _not_ be relevant; it's full of useful and even vital diagnostic information, such as $PATH, to name but one Ah, my turn to play dumb. I didn't realize that set;export will actually print out the environment and the exported names. Moreover, I didn't realize it'll do so under /bin/sh as well. Oh, well, ignore that last comment about set;export, please... Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing. -- Dr. Jubal Harshaw -- 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/
Re: Cron problem/Documentation and Setup
Igor Pechtchanski wrote: On Wed, 18 Aug 2004, Andrew DeFaria wrote: Larry Hall wrote: 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! [snip] 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 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 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. Well initially it was a Perl script that I'm trying to run through cron. But I then stripped it down to just: #!/bin/bash echo testme /tmp/debug.log 21 Nothing additional got written into /tmp/debug.log. You have, of course, reviewed Yes I have but there was nothing there. Changed myscript to echo to /tmp/myscript.log so as not to have any problems with other things writing to /tmp/debug.log. No /tmp/myscript.log file was created. Problem reports: http://cygwin.com/problems.html and thought of attaching the output of cygcheck -svr, right? Yeah I thought about it! :-) OK I've attached it Also, did you try cron_diagnose.sh (Google for it)? I suspect some or all of your mounts may not be visible to cron... cron_diagnose.sh did point out that my /etc/passwd and /etc/group lacked read permission! Well it didn't actually lack read permission rather it was a symlink to network share. Actually it was a mount to a network share. So apparently I can't link passwd and group (I know, I know you hardliners will say You shouldn't symlink such things to network locations! What happens if the network is down and you try to login? - well I'm already logged into Windows so there is no real login happening under Cygwin. Yes there is a risk if the network is down then I will not have passwd, group, etc. Then again, whenever the network is down I'm either not working or working on the network problem anyway, but I digress..). Switched this to local copies. Now some things are working better. Do your cron jobs above (i.e., 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 ) still work correctly after changing ls to /bin/ls? Does changing /tmp/myscript to sh -c '/tmp/myscript' help any? With local /etc/passwd and /etc/group I'm able to execute /tmp/myscript. However I wish to execute ~/bin/somescript. I can't seem to get to $HOME! Now 'round here they map the P drive to the home share via //server/username$ - yeah that dollar sign thingy in Windows. I had done a mount -bsf //server/$USERNAME\$ /home a long time ago. However trying to ls /home/bin doesn't work in cron. Neither does ls P: nor even ls //server/$USERNAME\$! This can be seen by the following output: Executing myscript TPAD3741 \\rtnlprod02\viewstore\webtest\CM_DOCS\Web on /wwwtest type system (binmode) \\rtnlprod02\viewstore\webview\CM_DOCS\Web on /www type system (binmode) \\rtnlprod02\viewstore\PMO\CM_TOOLS on /pmo type system (binmode) \\isdata01\TPAD3741$ on /home2 type system (binmode) C:\Program Files on /apps type system (binmode) C:\Cygwin\bin on /usr/bin type system (binmode) C:\Cygwin\lib on /usr/lib type system (binmode) C:\Cygwin on / type system (binmode) M: on /view type system (binmode) P: on /home type system (binmode) b: on /dev/b type system (binmode,noumount) c: on /dev/c type system (binmode,noumount) New connections will be remembered.^M Status Local RemoteNetwork^M --- M:\\viewClearCase Dynamic Views \\view\defariaClearCase Dynamic Views The command completed successfully.^M ls: p:: No such file or directory ls: //isdata01/TPAD3741$: No such file or directory End of myscript For some reason the P drive is not available to cron at all (Note at a previous company I was able to get to my home share merely by using the mount -bsf //server/share to /home and refering to /home/$USERNAME for the $HOME variable. Here they do not export a share under which all users reside, rather they map, probably from ntlogin.bat, the specific, hidden $USERNAME share directly to the
Re: Cron problem/Documentation and Setup
At 10:44 PM 8/18/2004, you wrote: So is P or /home off limits when it comes to cron? Why did this work at my last company? I think it's probably due to the public share point versus non-public share point (which I never totally understood before) and I'm fearing that I will not be able to convince the powers that be to change it! :-( Bingo! You can always resort to running cron as you instead of 'SYSTEM'. As long as you're the only user that needs to run under 'cron', that should work without changing the permissions of your network shares. -- 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/
Re: Cron problem/Documentation and Setup
Larry Hall wrote: At 10:44 PM 8/18/2004, you wrote: So is P or /home off limits when it comes to cron? Why did this work at my last company? I think it's probably due to the public share point versus non-public share point (which I never totally understood before) and I'm fearing that I will not be able to convince the powers that be to change it! :-( Bingo! You can always resort to running cron as you instead of 'SYSTEM'. As long as you're the only user that needs to run under 'cron', that should work without changing the permissions of your network shares. I'd hate to have to resort to that! This doesn't explain why it worked at my last company and why I could have sworn it used to work here up until about a week ago. -- Do illiterate people get the full effect of alphabet soup? -- 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/
Re: Cron problem/Documentation and Setup
At 11:13 PM 8/18/2004, you wrote: Larry Hall wrote: At 10:44 PM 8/18/2004, you wrote: So is P or /home off limits when it comes to cron? Why did this work at my last company? I think it's probably due to the public share point versus non-public share point (which I never totally understood before) and I'm fearing that I will not be able to convince the powers that be to change it! :-( Bingo! You can always resort to running cron as you instead of 'SYSTEM'. As long as you're the only user that needs to run under 'cron', that should work without changing the permissions of your network shares. I'd hate to have to resort to that! This doesn't explain why it worked at my last company and why I could have sworn it used to work here up until about a week ago. Well, if you can check the access permissions on the share in question, you should be able to determine whether this is an issue or not. -- 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/
Cron problem/Documentation and Setup
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: $ 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! 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 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 Here's the result: /var/cron tabs -rwxrwxrwx1 TPAD3741 Domain U 5201 Aug 17 17:15 /tmp/myscript /tmp/myscript never get's executed. -- Okay, who put a stop payment on my reality check? -- 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/
Re: Cron problem/Documentation and Setup
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 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 Here's the result: /var/cron tabs -rwxrwxrwx1 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/
Re: Cron problem/Documentation and Setup
At 10:38 PM 8/17/2004, you wrote 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 21 19 17 * * * ls /tmp/debug.log 21 20 17 * * * ls -l /tmp/myscript /tmp/debug.log 21 21 17 * * * /tmp/myscript /tmp/debug.log 21 Here's the result: /var/cron tabs -rwxrwxrwx1 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. ^^^ is 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/
