Peter Tribble wrote: > Cron is the service. Crontabs are just data. Everything is just data. /etc/inittab, /etc/rc*.d files, and /etc/inetd.conf are just data; why did they get imported into SMF?
What matters is what use you make of the data. Crontab jobs define persistent, long-term specifications for running processes under specified circumstances and in specified environments. That sounds like *exactly* what startd and inetd do. > (Waiting for the day someone suggests that smf becomes a mail spool. > It provides service guarantees right, so each message is a service and > smf is responsible for reliable delivery.) First, you're being silly. Second, messages are one-time events, which is pretty fundamentally different from the things we're talking about here. That is, BTW, the main reason that I'm not at all sure that "at" fits into SMF. Now, if we wanted to put "at" jobs, messages, and print jobs all into the same queueing infrastructure, I might see it... but probably not, and I don't want to go there.
