X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 06 Nov 2007 10:53:14 -0500 From: "Pierre A. Humblet" Subject: Re: cron problems To: =?iso-8859-1?Q?Helge_Stenstr=F6m?= , Message-id: <03b101c8208d$24dcb220$b40410ac@wirelessworld.airvananet.com> MIME-version: 1.0 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT References: <539508700711060648m97c743fya8417d274c5c28f5 AT mail DOT gmail DOT com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 ----- Original Message ----- From: "Helge Stenström" <> To: Sent: Tuesday, November 06, 2007 9:48 AM Subject: cron problems | I no longer remember the exact questions, but there are some issues. Yes, there always are issues but I am not sure why. | 1. cron-config asked about my password, and it was visible in | cleartext when I entered it. Is that a bug? I would be happy to improve the cron-config script if someone proposes a simple solution. | 2. What is the password used for? A policy forces me to change | password on my Windows account every 60 days. Will the cron daemon try | to use the old password, so that I will be locked out from the | account? If that happens, it will be difficult to fix, because I | cannot login. If you run cron as yourself, Windows requires a password. Windows will enforce your system policy. Your system administrator can change it. | 3. After I enabled cron, I installed a program. It took much longer | than expected, 35 minutes instead of 2-5 minutes. Meanwhile, there | were many (> 10 each) processes that used a lot of memory: | | cron.exe (1.5M) | sh.exe (3.6M) | | I manually killed these processes, and the intallation could finally finnish. | The crontab at this time consisted of "touch filename" every minute. | Shouldn't load the CPU. | Is this a known issue? The amount of memory per process looks normal. But how many cron.exe processes did you see? Were the sh processes running under cron? If there is a bug it's more likely to be in your cron jobs than in cron itself. Have them produce some output so you can figure out what they do and how long it takes. Pierre -- 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/