Subject: Re: /var/cron -> /etc/cron
To: Curt Sampson <firstname.lastname@example.org>
From: Brian Buhrow <email@example.com>
Date: 04/01/1999 23:44:13
Actually, I object because cron files are unique to each machine, or
rather, they can be. Now with dhcp doing network configuration, /etc can
be completely replicated across systems without fear of having to keep
track of machine differences. Also, most other systems put cron in /var,
somewhere, and I feel like this is just another gratuitous difference from
every other *nix implementation out there. As the least popular *nix on
the list of free Os's already, I'd hate to see another reason for not using
NetBSD get added to the list. This is not a big issue on this point, but
it is another straw.
On Apr 1, 9:58pm, Curt Sampson wrote:
} Subject: /var/cron -> /etc/cron
} I've got minor tweaks to various files so that the following
} conversions happen:
} /var/cron/tabs -> /etc/cron/tabs
} /var/cron/log -> /var/log/cron
} /var/cron itself disappears.
} The rationale behind this is that there's no reason to keep cron
} logfiles separate from other logfiles, and crontabs themselves are
} vital configuration information that should be preserved forever
} (rather than `spool' information), and thus belong in /etc.
} Any objections to me commiting this to current? Any suggestions on
} how to ease the transition for users?
} Does anyone feel strongly that this should be in 1.4? I think it's
} fairly low risk myself, but I'll defer to whatever others think.
} Curt Sampson <firstname.lastname@example.org> 604 801 5335 De gustibus, aut bene aut nihil.
} The most widely ported operating system in the world: http://www.netbsd.org
>-- End of excerpt from Curt Sampson