From owner-freebsd-current Fri Aug 20 22: 0:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 7953E14F02 for ; Fri, 20 Aug 1999 22:00:11 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id EAA27932; Sat, 21 Aug 1999 04:22:46 +0200 From: Luigi Rizzo Message-Id: <199908210222.EAA27932@labinfo.iet.unipi.it> Subject: Re: problem with vnconfig -s labels ... To: atrens@nortelnetworks.com (Andrew Atrens) Date: Sat, 21 Aug 1999 04:22:46 +0200 (MET DST) Cc: current@freebsd.org In-Reply-To: from "Andrew Atrens" at Aug 20, 99 02:14:54 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 480 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > I've found panics are more likely to occur if the command pair is > executed in a script vs. from the command line. This may suggest some > sort of race is occurring. no idea... i have always managed to panic the system even running the commands from the command line one at a time, so i don't think it is a race. I think i also got the paninc trying a disklabel when the "vn" device was not in the kernel, but this one i had no time to reproduce. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message