* Steve Greenland said: > > > No, *your* particular instance of Debian survived. *Your* crontabs > > > worked fine. > > Checked also on three other Debian systems. On each and every of them Vixie > > cron uses /bin/sh to execute those crontabs. *Always* > > You've still missed the point: proof by example is fundamentally flawed. > Saying "it works on my system (and a few others), therefore it will > work on all Debian systems" (which is what was implied by your original > statement) is not an acceptable argument. Come on! Will you spare a minute and actually read crond manpage? It says explicitly that crontabs are executed using /bin/sh UNLESS somebody modifies the environment. So what's the problem? > OTOH, an analysis of the affected subsystems ("cron uses /bin/sh to > execute crontabs, not root's shell") *is* a valid argument. But that's > not what you said originally. Well, I didn't want to repeat what was said. I assumed that you read the entire thread and Justin said just that - crond uses /bin/sh. > None the less, FWIW, I'm with Craig on this one: if you folks want to > set up some extra packages that result in a bunch of statically tools, > that's fine, but I strongly object to changing the base setup for such a > low value proposition (in my experience). That issue comes back all over again in this thread. But I think it's too early to discuss the politics, first the technical issues should be agreed upon only then where and how to install the package in the system... marek
Attachment:
pgp3kQ_1nUUXM.pgp
Description: PGP signature