From owner-freebsd-questions@FreeBSD.ORG  Fri May 28 16:07:52 2004
Return-Path: <owner-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 3050916A4CE
	for <freebsd-questions@freebsd.org>;
	Fri, 28 May 2004 16:07:52 -0700 (PDT)
Received: from cheyenne.wixb.com (cheyenne.wixb.com [65.43.82.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 918DE43D1D
	for <freebsd-questions@freebsd.org>;
	Fri, 28 May 2004 16:07:51 -0700 (PDT)
	(envelope-from jbronson@wixb.com)
Received: from thinkpad.wixb.com (thinkpad.wixb.com [10.43.82.5])
	i4SN7ExL000336;	Fri, 28 May 2004 18:07:14 -0500 (CDT)
Message-Id: <6.1.1.1.2.20040528180423.00bd1658@cheyenne.wixb.com>
Date: Fri, 28 May 2004 18:07:14 -0500
To: freebsd-questions@freebsd.org
From: "J.D. Bronson" <jbronson@wixb.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.43
Subject: ramdisk-own on 5.2.1
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2004 23:07:52 -0000

I have a script which was provided to me (from a PR log)
and its for ramdisk-ownership:

=============================================================
# PROVIDE: ramdisk-own
# REQUIRE: ramdisk mountcritlocal
# BEFORE: SERVERS
# KEYWORD: FreeBSD

. /etc/rc.subr

name="ramdisk"
stop_cmd=":"
start_cmd="ramdisk_own_start"

ramdisk_own_start()
{
set -x
         for unit in $ramdisk_units; do
                 device="/dev/md$unit"
                 dir=`mount | grep $device | cut -d' ' -f3`

                 eval owner=\$ramdisk_${unit}_owner
                 eval perms=\$ramdisk_${unit}_perms

                 [ "X$owner" != "X" ] && chown -f "$owner" $device 
$dir
                 [ "X$perms" != "X" ] && chmod -f "$perms" /dev/md$unit 
$dir
         done
}

load_rc_config $name
run_rc_command "$1"

=============================================================================

...however, this results is MESSY output to the console and log file(s):

Setting hostname: shadow.
+ device=/dev/md0
+ mount
+ grep /dev/md0
+ cut -d  -f3
+ dir=/tmp
+ eval owner=$ramdisk_0_owner
+ owner=root:wheel
+ eval perms=$ramdisk_0_perms
+ perms=1777
+ [ Xroot:wheel != X ]
+ chown -f root:wheel /dev/md0 /tmp
+ [ X1777 != X ]
+ chmod -f 1777 /dev/md0 /tmp
+ device=/dev/md1
+ grep /dev/md1
+ cut -d  -f3
+ mount
+ dir=/var/spool/MIMEDefang
+ eval owner=$ramdisk_1_owner
+ owner=defang:defang
+ eval perms=$ramdisk_1_perms
+ perms=0700
+ [ Xdefang:defang != X ]
+ chown -f defang:defang /dev/md1 /var/spool/MIMEDefang
+ [ X0700 != X ]
+ chmod -f 0700 /dev/md1 /var/spool/MIMEDefang
+ _return=0
+ [ 0 -ne 0 ]
+ [ -n  ]
+ return 0


...but it does work 100%. Is there any way of 'cleaning' this up so that 
one does not see these messages, but that the work is DONE?



-- 
J.D. Bronson
Aurora Health Care // Information Services // Milwaukee, WI USA
Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282