From owner-freebsd-doc Sun Mar 17 11:40: 4 2002 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E7C9C37B421 for ; Sun, 17 Mar 2002 11:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2HJe1I25584; Sun, 17 Mar 2002 11:40:01 -0800 (PST) (envelope-from gnats) Date: Sun, 17 Mar 2002 11:40:01 -0800 (PST) Message-Id: <200203171940.g2HJe1I25584@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: swear@blarg.net (Gary W. Swearingen) Subject: Re: docs/35943: at(1) config files are misplaced in /var/at/ Reply-To: swear@blarg.net (Gary W. Swearingen) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR docs/35943; it has been noted by GNATS. From: swear@blarg.net (Gary W. Swearingen) To: Giorgos Keramidas Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: docs/35943: at(1) config files are misplaced in /var/at/ Date: 17 Mar 2002 11:34:49 -0800 Giorgos Keramidas writes: > There are other programs that use /var too. Cron(8) for instance, saves > the crontabs in /var/cron/tabs. Why is it so bad that at(1) saves files in > /var too? It's NOT bad that programs SAVE files in /var/; that's what it's there for. And /etc/ is there for read-only config files. But the cron(8) and at(8) programs are the only ones I know of that read from read-only configuration files in /var/. (I was saving cron(8) until I saw how at(1) went, but only for cron's "allow" and "deny", not its databases.) Of course, it is debatable whether it is better to keep a program's files together or scatter them about, or whether it's useful to distinguish between config files and database files the crontabs, but I think that in one of these rare cases where there is a clear rule or convention, it should be adhered to by all system programs when it's practical; in this case it's easy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message