From owner-freebsd-isp@FreeBSD.ORG  Sun Mar  7 18:43:56 2004
Return-Path: <owner-freebsd-isp@FreeBSD.ORG>
Delivered-To: freebsd-isp@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6E35E16A4CE
	for <freebsd-isp@freebsd.org>; Sun,  7 Mar 2004 18:43:56 -0800 (PST)
Received: from destiny.chrononomicon.com (mail.chrononomicon.com
	[65.193.73.208])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0207B43D45
	for <freebsd-isp@freebsd.org>; Sun,  7 Mar 2004 18:43:56 -0800 (PST)
	(envelope-from bsilver@chrononomicon.com)
Received: from [IPv6:::1] (destiny.chrononomicon.com [192.168.1.42])
	by destiny.chrononomicon.com (Postfix) with ESMTP id 85AAC1FDFF
	for <freebsd-isp@freebsd.org>; Sun,  7 Mar 2004 21:43:51 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Transfer-Encoding: 7bit
Message-Id: <74A5A8EA-70AA-11D8-93D4-000A956D2452@chrononomicon.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: freebsd-isp@freebsd.org
From: Bart Silverstrim <bsilver@chrononomicon.com>
Date: Sun, 7 Mar 2004 21:44:01 -0500
X-Mailer: Apple Mail (2.612)
Subject: Perc3 utility
X-BeenThere: freebsd-isp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Internet Services Providers <freebsd-isp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isp>
List-Post: <mailto:freebsd-isp@freebsd.org>
List-Help: <mailto:freebsd-isp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Mar 2004 02:43:56 -0000

Is anyone out there running FreeBSD 4.9-RELEASE with the Dell aaccli 
utility?  If so, are you able to run successful cron scripts that 
invoke that command?

I have a script that whenever it's run, the aaccli command "hangs", but 
when I run the command line Cron is invoking as root (with sh, it's 
running with root's crontab entry) it works just fine.  I haven't found 
what the difference is between Cron's environment running root's 
crontab entry and root running the same command from /bin/sh...