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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: "Dylan Cuthbert" Subject: Re: long timeouts on shutdown/log off Date: Wed, 22 Oct 2003 12:17:03 +0900 Lines: 39 Message-ID: References: <20031017153138 DOT GB10560 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Ok, more info The cron tasks are running as normal when I try to log off, its just that windows can't forcibly terminate them when it tries to close everything and has to sit there waiting for the cron jobs to finish (can be up to 30 minutes for backing up a lot of changes). The pre-20th September version of cygwin has no problem terminating the cron jobs (I still have several machines running that version and the same script), so what's changed in the latest version to cause this? I'm beginning to suspect It probably is to do with Pierre's permission stuff. Because the cron jobs are run from a daemon running as SYSTEM, the user log off procedure can't kill the parent task, but the children tasks *are* user tasks and maybe it can't kill these because they were created by SYSTEM? Just clutching at straws as right now I don't have my backup system working (unless I put up with 30 minute logoff times) and I want it back :-( Any help much appreciated. --------------------------------- Q-Games, Dylan Cuthbert. http://www.q-games.com "Christopher Faylor" wrote in message news:20031017153138 DOT GB10560 AT redhat DOT com... > On Fri, Oct 17, 2003 at 07:50:34PM +0900, Dylan Cuthbert wrote: > >Ok, here are the ps results... I can see three cron tasks with the I field > >set (Interactive?) which is very odd as my backup script doesn't have any > >input (I've attached the script and the output) > > 'I'nput. That would indicate that cron is waiting for some kind of file I/O. > > cgf > -- 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/