X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=N5jo4aBWqyGIVGnMoRoI76ByDipQADZPh7CgqrKY6zP 1+4vSP9fygbWgkshsiLPyjKJFinCxBcLHt2B/RPKu8NmYiQ60r2QAZe2yJpoQ5nm 44is4CATiqooZgoKyW0Zp9Lr4rRlEbygBqXlAjQS2KWcfNa2vlBz9b2zpvlr6WMY = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=hGOOx+JtRf9QQe/OUsa9yQOt8M0=; b=j/mS8UKbjWAXrpoKm zBkVtbsdkO5R+m9S9FZTXe9FVD629h1jgTuNEMAX+hP8kaZVI2RY40mNDmeZcXHu NWMSAnhDEgX1/9bx5dmsGpe6YaJNr52iYfBjLv2dXXRk7M/kXVgVfsnUJMdw89gA oTVrEuKNu2IS5yho64K4EWff4k= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: <cygwin.cygwin.com> List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com> List-Archive: <http://sourceware.org/ml/cygwin/> List-Post: <mailto:cygwin AT cygwin DOT com> List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: Yes, score=5.3 required=5.0 tests=AWL,BAYES_50,RCVD_IN_PBL,RCVD_IN_RP_RNBL,RCVD_IN_SEMBLACK autolearn=no version=3.3.2 X-HELO: konqorde.nl Message-ID: <5241CBA1.7000405@mailme.ath.cx> Date: Tue, 24 Sep 2013 19:28:01 +0200 From: bartels <bartels AT mailme DOT ath DOT cx> User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130704 Icedove/17.0.7 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Confused about several issues with setting up cron References: <B8D164BED956C5439875951895CB4B2211449DC8 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> <523F133D DOT 2060806 AT mailme DOT ath DOT cx> <523F48E1 DOT 8070905 AT mailme DOT ath DOT cx> <B8D164BED956C5439875951895CB4B221145A863 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> <B8D164BED956C5439875951895CB4B2211477D08 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> In-Reply-To: <B8D164BED956C5439875951895CB4B2211477D08@WABOTH9MSGUSR8C.ITServices.sbc.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 09/24/2013 05:04 PM, KARR, DAVID wrote: >> -----Original Message----- >> From: KARR, DAVID >> Sent: Sunday, September 22, 2013 2:32 PM >> Subject: RE: Confused about several issues with setting up cron >> >>> -----Original Message----- >>> Sent: Sunday, September 22, 2013 12:46 PM >>> Subject: Re: Confused about several issues with setting up cron >>> >>> On 09/22/2013 05:56 PM, bartels wrote: >>>> On 09/22/2013 03:00 AM, KARR, DAVID wrote: >>>>> CYGWIN_NT-6.1 1.7.25(0.270/5/3) 2013-08-31 20:39 i686 Cygwin >>>>> >>>>> I want to set up a cron job, so I have to get cron configured. I'm >> trying >>> to follow the instructions I can find, but I'm seeing several issues. >>>>> I'm surprised that there's nothing in the user guide or the FAQ about >>> setting up cron. I had to settle for the various questions about this >>>>> on StackOverflow and others. >>> >>> I want to set up a cron job, so I have to get cron configured. I'm >>> trying >>> >> to follow the instructions I can find, but I'm seeing several issues. >>> >>> I'm surprised that there's nothing in the user guide or the FAQ about >>> >> setting up cron. I had to settle for the various questions about this >> on >>> >> StackOverflow and others. >>> >> >>> >> Must say your reporting of events is also lacking crucial elements >>> >> If you re-install and give me more details, then I will try and answer >>> your >>> >> questions. >>> > Ok. I assume you mean re-installing cron, not Cygwin. >>> Yes, cron-config is what I meant. >>> > >>> > I followed the process described in the FAQ for removing a service. I >>> then ran cron-config again. When I did this before, I selected to run >>> cron as myself. I decided to make it run as the local system account this >>> time (first running "passwd -R" and entering my password). It >>> appeared to complete without errors or warnings. I did this in a "run as >>> administrator" window. >>> > >>> > In a normal window, I then ran "crontab -e". I figured this would put >> me >>> into "vi" with an empty buffer. It just returned to the prompt. >>> You should see a vi session. >>> Do you have vi installed? >>> What is the value of EDITOR? >> Yes, I have vi installed. EDITOR was blank, but I tried setting it to "vi" >> and repeating the test, with no change. >> >>> This could indicate a deeper problem, confusing not just cron. >>> >>> > I then ran "crontab crontab" (the "crontab" file in my current directory >>> is the file with the one job I want to run), and then did "crontab >>> -l". Nothing. >>> >>> Are you familiar with the crontab format? If not, try this: >>> $ man 5 crontab >> Yes, I am familiar with it, but here's the crontab I'm trying to set, in any >> case: >> >> 0 * * * * monitorDataSource >> >>> > >>> > I then went back to the administrator window. I ran "cronevents". This >>> didn't show anything more than the cron service being started. I >>> then ran "cronbug". I'm attaching the gzipped copy of this. >>> > >>> You will have more luck running cron 'as yourself': it is straightforward. >>> Running it as a privileged user is more complicated. >>> >>> Is there a specific reason why you want to run it as system? >> No, only because running it as myself didn't work. >> >> In any case, I tried stopping and removing the service and rerunning cron- >> config, running the service as myself. It didn't make any difference. No >> response from "crontab -e", and "crontab crontab" seemingly ignored. Nothing >> in "/var/log/cron.log", and nothing in "cronevents" except for the service >> stopping and starting. > Any more ideas about this? > I guess it is to do with privileges. cron works on my machines without fail: as system, and as privileged user If you look at the service $ cygrunsrv.exe -Q cron --verbose You can see that you can run cron from your own account like this: $ /usr/sbin/cron -n Anyway, the cron process needs read/write access to /var/cron/tabs/<your account> No cron file there, means no cron jobs for you. The fact that you do not get an editor with 'crontab -e' is strange. I can only guess that EDITOR has a strange value, or crontab dies on privileges. Have you tried strace? $ strace -f crontab -e 2>&1 | tee strace.log You can probably see it dying. - bartels -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple