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 Reply-To: From: "Bill McCormick" To: Subject: RE: problem starting cron as a service Date: Mon, 21 Jul 2003 16:21:35 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal Ok, I missed the -D param. Just going from the man pages, cron takes no params. I also didn't find any info regarding running cron as a service in the /usr/doc's. So, as always, it's the littlest things that bite. Any idea regarding my previous post about ImageMagick? thanks mucho, Bill > -----Original Message----- > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf > Of Bowden, Todd > Sent: Monday, July 21, 2003 3:21 PM > To: 'cygwin AT cygwin DOT com' > Subject: RE: problem starting cron as a service > > > You have to install it as a service in order to see in from a Windows > perspective. > > cygrunsrv -I cron -p /usr/sbin/cron -a -D > Cygrunsrv -S cron > > net start | grep -i cron > > I see it in my Services. Why wouldn't you see it in yours > > The doc /usr/doc/Cygwin/cron.README tells you how to install it. > > Todd C. Bowden > HP Certified > AtosOrigin > 5000 S. Bowen > Arlington, TX 76017 > Office: 817-264-8211 > E-mail: Todd DOT Bowden AT atosorigin DOT com > > > -----Original Message----- > From: Bill McCormick [mailto:wpmccormick AT covad DOT net] > Sent: Monday, July 21, 2003 3:12 PM > To: cygwin AT cygwin DOT com > Subject: RE: problem starting cron as a service > > > Oops ... my bad. > > It's running; it's just not displayed as running as a service to > windows. ps > -x -f shows the grand truth. That being the case, doesn't cron startup > really belong in rc.local? Umm ... does rc.local even get called on system > boot? > > Thanks, > > Bill > > > -----Original Message----- > > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On > > Behalf Of Vince Hoffman > > Sent: Monday, July 21, 2003 11:10 AM > > To: cygwin AT cygwin DOT com > > Subject: RE: problem starting cron as a service > > > > > > Opps thought from your previous message you already knew or i would > > have said. the easiest way is the "at" trick, from a command line,type > > "at \\yourcomputername 15:49 /interactive cmd.exe" > > this will give you a cmd shell running as SYSTEM. from there cd to your > > cygwin\bin directory and type "bash --login -i" which will give > you a bash > > shell running as SYSTEM. > > > > > -----Original Message----- > > > From: Bill McCormick [mailto:wpmccormick AT covad DOT net] > > > Sent: 21 July 2003 16:41 > > > To: cygwin AT cygwin DOT com > > > Subject: RE: problem starting cron as a service > > > > > > > > > How do I run a prog as localsystem? > > > > > > > -----Original Message----- > > > > From: cygwin-owner AT cygwin DOT com > > > [mailto:cygwin-owner AT cygwin DOT com]On Behalf > > > > Of Vince Hoffman > > > > Sent: Monday, July 21, 2003 9:38 AM > > > > To: 'wpmccormick AT covad DOT net'; 'cygwin AT cygwin DOT com' > > > > Subject: RE: problem starting cron as a service > > > > > > > > > > > > Hi Bill, > > > > Off hand there are a few things to try, but Mark Harig > > > on the cygwin > > > > list seems pretty up on cron, and has a script which will > > > diagnose common > > > > problems, heres a link to a message which has it attached, > > > > > > > > > > > > You'll do better keeping messages on list as theres a > > > whole lot more > > > > experience out there than I have. One thing you could try > > > is running cron > > > > manualy from the command line as localsystem and seeing if you get > > > > any clues in the output. (appologys if you have and i missed that > > > > message.) > > > > > > > > Vince > > > > ps. the output of cygcheck -s -v -r as an uncompressed attachment > > > > might help too. > > > > > -----Original Message----- > > > > > From: Bill McCormick [mailto:wpmccormick AT covad DOT net] > > > > > Sent: 21 July 2003 15:18 > > > > > To: Vince Hoffman > > > > > Subject: RE: problem starting cron as a service > > > > > > > > > > > > > > > Thanks Vince, > > > > > > > > > > Nothing in cron.log (file created but empty) and mount is > > > > > system. Any other ideas? > > > > > > > > > > > > > > > Bill > > > > > > -----Original Message----- > > > > > > From: cygwin-owner AT cygwin DOT com > > > > > [mailto:cygwin-owner AT cygwin DOT com]On Behalf > > > > > > Of Vince Hoffman > > > > > > Sent: Monday, July 21, 2003 4:08 AM > > > > > > To: 'wpmccormick AT covad DOT net'; Cygwin > > > > > > Subject: RE: problem starting cron as a service > > > > > > > > > > > > > > > > > > anything in /var/log/cron.log ? > > > > > > > > > > > > and are you mounts system or user ? > > > > > > ie. > > > > > > $ mount |grep "/ type system" > > > > > > > > > > > > should give something like > > > > > > > > > > > > h:\cygwin on / type system (binmode) > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Bill McCormick [mailto:wpmccormick AT covad DOT net] > > > > > > > Sent: 21 July 2003 08:25 > > > > > > > To: Cygwin > > > > > > > Subject: problem starting cron as a service > > > > > > > > > > > > > > > > > > > > > I get this in the win app error log: > > > > > > > > > > > > > > Event Type: Error > > > > > > > Event Source: cron > > > > > > > Event Category: None > > > > > > > Event ID: 0 > > > > > > > Date: 7/21/2003 > > > > > > > Time: 2:14:08 AM > > > > > > > User: BILLHOME\Administrator > > > > > > > Computer: BILLHOME > > > > > > > Description: > > > > > > > The description for Event ID ( 0 ) in Source ( cron ) cannot > > > > > > > be found. The local computer may not have the necessary > > > > > > > registry information or message > > > > > > > DLL files to display messages from a remote computer. The > > > > > following > > > > > > > information is part of the event: cron : PID 2276 : starting > > > > > > > service `cron' > > > > > > > failed: execv: 0, No error. > > > > > > > > > > > > > > While trying to start the service as Administrator (or from > > > > > > > LocalSytems account). I rm'd /var/run/cron.pid and > > > > > > > /var/log/cron.log before trying to > > > > > > > start. > > > > > > > > > > > > > > Thanks > > > > > > > --- > > > > > > > Outgoing mail is certified Virus Free. > > > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > > > Version: 6.0.502 / Virus Database: 300 - Release > > > Date: 7/18/2003 > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > 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/ > > > > > > > > > > > > > > > > -- > > > > > 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/ > > > > > > > > > > > > > > > --- > > > > > Incoming mail is certified Virus Free. > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > > > > > > > --- > > > > Outgoing mail is certified Virus Free. > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > > > > > > > > -- > > > 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/ > > > > > > > > > --- > > > Incoming mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > > > > -- > > 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/ > > > > -- > > 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/ > > > > > > --- > > Incoming mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > > > -- > 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/ > > -- > 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/ > > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.502 / Virus Database: 300 - Release Date: 7/18/2003 -- 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/