From owner-freebsd-questions@FreeBSD.ORG Tue Jun 13 16:29:30 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C60D16A473 for ; Tue, 13 Jun 2006 16:29:30 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (dsl081-142-072.chi1.dsl.speakeasy.net [64.81.142.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id E968A43D45 for ; Tue, 13 Jun 2006 16:29:25 +0000 (GMT) (envelope-from derek@computinginnovations.com) Received: from p17.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.13.6/8.12.11) with ESMTP id k5DGT427081322; Tue, 13 Jun 2006 11:29:04 -0500 (CDT) Message-Id: <6.0.0.22.2.20060613112719.02719c70@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Tue, 13 Jun 2006 11:28:58 -0500 To: Jim Pazarena , freebsd-questions@freebsd.org From: Derek Ragona In-Reply-To: <448EDB17.6040305@ccstores.com> References: <448EDB17.6040305@ccstores.com> Mime-Version: 1.0 X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: cron job limits X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2006 16:29:30 -0000 Is your shell different from the account running the cron job? Is there any other jobs that might kill this cron job? Add echo statements to your script and save a log file. Be sure to redirect stderr as well as stdout to the log file. -Derek At 10:34 AM 6/13/2006, Jim Pazarena wrote: >I have a fairly lengthy routine which runs each >Sunday morning in a cronjob. For many months >now it has never completed, and I have to manually >run it from the CLI. (which runs fine). The cronjob >runs as root. > >It isn't failing because of a PATH problem, >(it's just /usr/local/bin/analog running in dozens >of repetitions) > >/usr/bin/limits shows most limits as infinity > >I don't get any email error message .. nothing! it just quits! > >any ideas? > >Thanks > > >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > >-- >This message has been scanned for viruses and >dangerous content by MailScanner, and is >believed to be clean. >MailScanner thanks transtec Computers for their support. > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.