Date: Sat, 25 Apr 1998 01:45:31 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: allen campbell <allenc@verinet.com> Cc: config@FreeBSD.ORG Subject: Re: Config Databases Message-ID: <17661.893493931@time.cdrom.com> In-Reply-To: Your message of "Sat, 25 Apr 1998 02:35:16 MDT." <199804250835.CAA19174@const.>
next in thread | previous in thread | raw e-mail | index | archive | help
> Jordan, this is dubious. First, as a result of a simple typo you > get to lose your work (assuming you are not using merely a working > copy.) Second, you are given no clue as to why. Lets call it Again, only if you edit the *wrong* copy. In fact, why are we even arguing about mis-editing /etc/passwd? It should be read-only! :-) As to the other files you might screw up the formatting of, I would propose that rather than leave these nasty little .err files around (one is reminded of core dumps come back to haunt in another even more horrible incarnation :-) you simply log the messages to syslog. Then I can use syslog.conf to more flexibly route those messages to another host or have them chatter on people's consoles or _whatever_ it is I want to do with them. But this conversation has veered off at an undesirable tangent - we didn't start out to discuss what kinds of comments might be left in a file or how one might log failures, that's really a gravy decision anyway, what we started off discussing was what *errors would be returned* by open/close/read/write on failures that were really "misconfiguration errors." That's when I started arguing for simply returning a normal status and leave the errno setting to truly obvious/fatal I/O errors, not trying to hand back to vi a confusing errno just because a field was mis-entered. That's the can of worms we've already discussed. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17661.893493931>