On 4 April 2011 15:09, Olaf van der Spek <olafvds...@gmail.com> wrote: > On Sun, Apr 3, 2011 at 9:06 PM, Javier Fern?ndez-Sanguino Pe?a > Network being available isn't really a corner case. > Isn't cron output mailed? What happens with that if the network (and > mail server) are not yet available?
(I really feel like you want to put argument after argument without thinking them through, I'll bite, but just this once). Yes, cron output is mailed, but the mailing system does not actually require the network to be up. Mail can be: a) to local user (this is the case for most cronjobs output as they are sent to root or whomever root points to in /etc/aliases) - in this case no network connection is required as the e-mail is delivered to the user b) to a remote user (this is the case when /etc/aliases points to an Internet e-mail or a .forward or .procmail rule is introduced) - in this case, again, no network connection is required, the mail is spooled and the e-mail subsytem will deliver it as soon in the next quere run, as it it finds it possible to make a connection with it's upstream MTA (if configured a gateway) or to the remote MTA (if not). So, you see, the fact that cron's output is sent through e-mail does not require the cron daemon to wait for the network being up and available at boot time before it starts. Regards Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
