On Sun, Apr 3, 2011 at 9:06 PM, Javier Fern?ndez-Sanguino Pe?a <j...@debian.org> wrote: >> How do I, as non-root user, ensure the net is available when my job runs? > > There are many ways. You could use 'network-test' from ifupdown-extra, or > write > your own tests.
And then do a busy-loop until the net is available? > The disadvantage is that we introduce cruft to cover corner cases. 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? > If we go through that path then we should add *all* possible subsystems to > the Should-Start of cron because *any* user can add a @reboot task that > depends on some other things. Actually, for best performance, cron should start as late as possible. > Sorry, but this is not something we are going to do. This bug stays closed. Yes boss -- Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
