From owner-freebsd-security Sat Feb 28 22:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29829 for freebsd-security-outgoing; Sat, 28 Feb 1998 22:44:35 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from kjsl.com (Limpia.KJSL.COM [198.137.202.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29816 for ; Sat, 28 Feb 1998 22:44:32 -0800 (PST) (envelope-from javier@kjsl.com) Received: (from javier@localhost) by kjsl.com (8.8.5/8.8.5) id WAA18503; Sat, 28 Feb 1998 22:44:25 -0800 (PST) Date: Sat, 28 Feb 1998 22:44:25 -0800 (PST) Message-Id: <199803010644.WAA18503@kjsl.com> From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Robert Watson Cc: Javier Henderson , Christopher J Ceska , freebsd-security@FreeBSD.ORG Subject: Re: Question In-Reply-To: References: <199803010551.VAA18342@kjsl.com> X-Mailer: VM 6.33 under Emacs 19.34.1 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk Robert Watson writes: > I'm not familiar with the VMS clustering behavior -- what services does it > provide? You can mount disk drives across the clusters. There's a distributed lock manager, which is what allows the transparent sharing of resources across the cluster members. Most clusters have a shared authorization file, though you can have node-specific files as well. You can have multiple hosts and disk drives on the same SCSI bus, and even if one node crashes, the remaining nodes' access to the disk drives remains undisturbed in most cases. Any node can also serve disk drives to the cluster, though of course those drives would go away if the node crashes. That's in a very small nutshell. There's lots more. -jav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message