Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 20 Sep 2004 14:07:49 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: =?ISO-8859-2?Q?Mogyor=F3si_Istv=E1n?= cc: cygwin AT cygwin DOT com Subject: Re: Crontab issue In-Reply-To: <414F15BE.3010203@tdc.hu> Message-ID: References: <414F15BE DOT 3010203 AT tdc DOT hu> MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY=------------020504030505020803090103 Content-ID: X-Scanned-By: MIMEDefang 2.39 --------------020504030505020803090103 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1; FORMAT=flowed Content-Transfer-Encoding: 8BIT Content-ID: On Mon, 20 Sep 2004, Mogyorósi István wrote: > Hello, > > I spent quite a lot of time reading the subject and I still dont have > clear sight on the problem. It is probably a permission/access sync > issue between Cygwin and NT. But my case is NOT a network drive. > > Case 1, > crontab -e [ logged in as Administrator ] > 20 12 * * * /home/Administrator/mydate.sh [ my own script to exec ] > ----- > it works with the result written in my home directory. > mydate.sh is `date >mydate.txt` It's a good idea to specify the absolute paths for any commands or output files. > Case 2, > crontab -e [ logged in as Administrator ] > 25 12 * * * /cygdrive/e/otherpath/mydate.sh [ my second script to exec ] > ------------- > this does not work. > My Error message in Eventlog is: > bla .. bla .. /usr/sbin/cron : PID 2356 : (Administrator) CMD > (/cygdrive/e/otherpath/mydate.sh 2>&1) Hmm, looks like it *is* getting executed, but the output is lost? See the previous comment. > The access permissions for both shell scripts are identical. > The only difference is the path to execute. Can you execute the latter script from the command line as Administrator? If not, are the access permissions on both *paths* sufficient? For a script to be executable, all the components in the path to it have to be reachable (i.e., the directories have to have at least the execute permission). > If I install the service as Administrator, and try to start it > with the Service Control Manager it fails to start and > I get the error message in the Event Log: > ... bla bla .. Cygwin_cron : PID 2260 : starting service > 'Cygwin_cron' failed : execv: 1 , Operation not permitted. This is a different symptom -- most likely the necessary DLLs in your /bin are not executable by non-owners (i.e., SYSTEM, which is the user cron will run under when installed as service). A "chmod -R a+X /bin" should help (you might also need to fix permissions for other files/directories under /var, and maybe /lib, /share, and /etc). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,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 --------------020504030505020803090103 Content-Type: text/plain; charset=us-ascii -- 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/ --------------020504030505020803090103--