Normally a "*.d" directory is for package-specific contributions to a config file that are all handled together by the configured facility -- Linux has logrotate.d for all the log rotating specs from different packages, and cron.d for specific cron additions, and so forth. Emacs recognizes an emacs.d directory for some startup file things, too.
Solaris has an /etc/cron.d directory, but the files in it aren't crontab files, and the man pages don't make any suggestion of anything except user-specific cron files (no system cron file, either, that I can find). So why the heck is the directory called /etc/cron.d? That's just mean; deliberately misleading people! And misusing the naming convention. And how much trouble is it to replace the archaic cron system with something with decent features? I suppose that would mess up all the package installations? (truth time: I'm going to be *so* happy when there's a decent ZFS implementation in Linux and I can ditch this archaic pile of kludges.) -- David Dyer-Bennet, [EMAIL PROTECTED]; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info _______________________________________________ opensolaris-discuss mailing list [email protected]
