From owner-freebsd-config Fri Apr 24 00:47:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15747 for freebsd-config-outgoing; Fri, 24 Apr 1998 00:47:50 -0700 (PDT) (envelope-from owner-freebsd-config@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15700 for ; Fri, 24 Apr 1998 00:47:43 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA04478; Fri, 24 Apr 1998 00:47:28 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Philippe Regnauld cc: allen campbell , config@FreeBSD.ORG Subject: Re: Config Databases In-reply-to: Your message of "Fri, 24 Apr 1998 09:32:59 +0200." <19980424093259.13767@deepo.prosa.dk> Date: Fri, 24 Apr 1998 00:47:27 -0700 Message-ID: <4474.893404047@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-config@FreeBSD.ORG Precedence: bulk > problem: how is the user supposed to know he made a mistake ? You ca He'll know it pretty conclusively, I think, when the change he just made mysteriously has no effect whatsoever and doesn't show up in the file. :) > In the first suggestion (silently bouncing) means there's not even > _trace_ of the mods, right ? Hmmm.. Right. I'm not saying that this behavior is ideal, far from it, I'm simply saying that this is the lowest-impact approach and will require the least programming headache. Unless we're all just discussing this as an intellectual exercise, of course, and there's no intention of actually implementing it in which case by all means let's discuss all the errors one might pass back on close() in hopes that the application will even check the return value. :-) Succeeding silently and using secret knowledge of the file format to tack in comments also strikes me as a cute but ultimately untenable workaround, so I really do vote for the simpler approach. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message