From owner-freebsd-questions@FreeBSD.ORG Tue Sep 8 13:05:39 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5752106566B for ; Tue, 8 Sep 2009 13:05:39 +0000 (UTC) (envelope-from stanb@panix.com) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.freebsd.org (Postfix) with ESMTP id 92D058FC23 for ; Tue, 8 Sep 2009 13:05:39 +0000 (UTC) Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by mail1.panix.com (Postfix) with ESMTP id BD9EB1F088; Tue, 8 Sep 2009 09:05:38 -0400 (EDT) Received: from teddy.fas.com (c-76-26-200-187.hsd1.sc.comcast.net [76.26.200.187]) by mailbackend.panix.com (Postfix) with ESMTP id 8D3A2348BE; Tue, 8 Sep 2009 09:05:38 -0400 (EDT) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 1Ml0O9-0004jg-00; Tue, 08 Sep 2009 09:05:37 -0400 Date: Tue, 8 Sep 2009 09:05:37 -0400 From: stan To: Mel Flynn Message-ID: <20090908130537.GA18048@teddy.fas.com> Mail-Followup-To: Mel Flynn , freebsd-questions@freebsd.org References: <20090903114857.GA635@teddy.fas.com> <200909032341.28748.mel.flynn+fbsd.questions@mailing.thruhere.net> <20090904142807.GA5339@teddy.fas.com> <200909041704.19865.mel.flynn+fbsd.questions@mailing.thruhere.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909041704.19865.mel.flynn+fbsd.questions@mailing.thruhere.net> X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.23 X-Uptime: 08:59:14 up 38 days, 14:01, 1 user, load average: 0.22, 0.17, 0.13 User-Agent: Mutt/1.5.4i Sender: Stan Brown Cc: freebsd-questions@freebsd.org Subject: Re: What invokes cricket on FreeBSD 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, 08 Sep 2009 13:05:40 -0000 On Fri, Sep 04, 2009 at 05:04:19PM +0200, Mel Flynn wrote: > On Friday 04 September 2009 16:28:07 stan wrote: > > On Thu, Sep 03, 2009 at 11:41:28PM +0200, Mel Flynn wrote: > > > On Thursday 03 September 2009 22:23:47 stan wrote: > > > > On Thu, Sep 03, 2009 at 10:10:13PM +0200, Mel Flynn wrote: > > > > > On Thursday 03 September 2009 21:02:41 stan wrote: > > > > > > pnoc# cat collect-subtrees > > > > > > #!/bin/sh > > > > > > > > > > > > echo STARTED >> /tmp/stan > > > > > > which perl >> /tmp/stan > > > > > > /usr/local/cricket/cricket/collect-subtrees.pl normal >> /tmp/stan > > > > > > echo Done >> /tmp/stan > > > > > > > > > > > > /tmp stan contains: > > > > > > > > > > > > pnoc# cat /tmp/stan > > > > > > STARTED > > > > > > /usr/bin/perl > > > > > > Done > > > > > > STARTED > > > > > > /usr/bin/perl > > > > > > Done > > > > > > > > > > > > So, cron is invoking the correct command, and perl can be found, > > > > > > but the original collect_subtrees perl script silently dies. > > > > > > > > > > > > I am convinced it's an environemt probkl`lem, I am just uncertain > > > > > > how to determine what. > > > > > > > > > > I'm not anymore. I'm putting 1 cent on a broken /usr/bin/perl symlink > > > > > (perl upgrade gone bonkers, f.e. done with ro mounted /usr) and > > > > > another cent on the perl script using system() function, with > > > > > pathless commands (that is environment). > > > > > > Ok, one liner: > > > su -m cricket env -i HOME=/usr/local/cricket PATH=/bin:/usr/bin \ > > > /usr/local/cricket/cricket/collect-subtrees.pl normal > > > > > > I've downloaded the 1.0.5 version, but can't quickly see where that would > > > go wrong with this script. touch is in /usr/bin, so that should work. Any > > > cron messages in /var/mail/cricket? > > > > I am away from work today, and won't be back till Tuesday. I can't access > > this from home. > > > > I will try your test then. The only messages that are getting to > > /var/log/cron is just the one saying that the task was executed. > Yea, the error messages end up in /var/mail/$USER or MAILTO variable if set in > crontab. /var/log/maillog should have some tell tales. That turned out to be the information I needed to solve theproblem. I had told my contractor to put a .forward in every non user uer'es account (such as Cricket), and he had not done that. had he done that I would have gotten the needed inforamtion, when I first brought the system abck up. Turns out there was a lockfile, and Cricket was emailing me, asking me to remove it if it was satle :-( Removing it solved the mystery. Thanks for all the help, everyone!! Subtree normal is currently being processed. If this is a mistake, use "rm /tmp/cricket-subtree-normal" to unlock it. -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs.