From owner-freebsd-questions@FreeBSD.ORG Thu Dec 17 04:19:24 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 5B954106568B for ; Thu, 17 Dec 2009 04:19:24 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 0E6188FC0C for ; Thu, 17 Dec 2009 04:19:23 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id nBH4JNQA098897; Wed, 16 Dec 2009 21:19:23 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id nBH4JNNw098894; Wed, 16 Dec 2009 21:19:23 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 16 Dec 2009 21:19:23 -0700 (MST) From: Warren Block To: Kevin In-Reply-To: <7314e5020912161917s355d02c9l16c996043c753044@mail.gmail.com> Message-ID: References: <7314e5020912161917s355d02c9l16c996043c753044@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (wonkity.com [127.0.0.1]); Wed, 16 Dec 2009 21:19:23 -0700 (MST) Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade failure 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: Thu, 17 Dec 2009 04:19:24 -0000 On Wed, 16 Dec 2009, Kevin wrote: [...] > The only other symptoms I can identify right now are related to the > following entries in my crontab: > > 0 2 * * 6 /usr/local/sbin/portsclean -DD > 0 2 * * 5 /usr/local/sbin/portsclean -C > > The e-mailed results simply say "env: ruby: No such file or > directory". However, these commands seem to run fine from an > interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: #!/usr/bin/env ruby That should find and run ruby. Your /etc/crontab should have these lines: SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin > I also receive the same message at the end of the output for > "/usr/sbin/portsnap cron update && /usr/local/sbin/portsdb -u > > /dev/null" run from cron: portsdb is another ruby script. Same deal; cron running env can't find ruby. -Warren Block * Rapid City, South Dakota USA