Date: Fri, 13 Jul 2001 15:13:25 -0400 (EDT) From: ahd@kew.com To: FreeBSD-gnats-submit@freebsd.org Subject: bin/28950: vinum uses the lock directory hierarchy inconsistent with FreeBSD Message-ID: <20010713191325.50859BA27@minerva.uucp.kew.com>
next in thread | raw e-mail | index | archive | help
>Number: 28950 >Category: bin >Synopsis: vinum uses the lock directory hierarchy inconsistent with FreeBSD >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jul 13 12:20:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Drew Derbyshire >Release: FreeBSD 4.3-RELEASE i386 >Organization: Kendra Electronic Wonderworks, Stoneham MA 02180 (http://www.kew.com) >Environment: System: FreeBSD minerva.hh.kew.com 4.3-RELEASE FreeBSD 4.3-RELEASE #0: Sat Jun 23 09:50:15 EDT 2001 root@:/usr/scratch/obj/usr/src/sys/MINERVA i386 Machine is using vinum for mirroring drives >Description: vinum uses /var/lock (no subdirectory) for its lock files, which is inconsistent with other components in the FreeBSD environment and non-descriptive (I had to run fstat to determine the owning program). (This also screws up muscle memory for those us of used to looking at FreeBSD logs with tcsh via "cd /var/l<TAB>" I would suggest the files should be under /var/db/vinum or /var/spool/lock/vinum (or another directort with vinum as the last component), but not at the root of the /var directory and not without vinum in the name. >How-To-Repeat: Start vinum on a FreeBSD system. >Fix: Move the directory. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010713191325.50859BA27>