Hello, I adopted the cron package a few months ago, and want to fix as many bug reports as possible. The current bug report is now quite twenty years old, which means, in terms of computer science, about ten eternities ;)
As no consensus has been achieved for twenty years to decide whether this a bu or a non-bug, and as sane workarounds do exist (make important scripts independent of environment variants), I shall close this bug now: I believe that it cannot be fixed by a single change in cron package. Of course, you can reopen it if necessary, but please be kind enough to propose new arguments (I mean newer than the already discussed stuff) Best regards, Georges. Loïc Minier a écrit : > Steve Greenland <ste...@moregruel.net> - Thu, Sep 23, 2004: > > > It was discussed a few years ago, when init (or the kernel) changed > > behaviour, and at the time, the consensus was that scripts like this are > > responsible for having their PATH. It's been a while, though, and that > > might have changed, but you might search the archives (sorry I don't > > have a reference, it's been a while). > > Don't waste your time searching for this, you really have a lot of > better things to do! :) > > I think I've already found the discussions[1]. Because they weren't > finished and did not result in inclusion in the Policy, I really ought > to move my behind and bring this up again in debian-policy, and this is > in preparation. > > > /* ... (save me from /etc/cron.conf!) ... (vix, jan90) */ > > Erf! > > > The problem with making it configurable is that the admin might change > > it, which means that package scripts can still not rely on it. > > Good point, but it is still useful when you're running scripts that are > making the assumption of a sane environment (as was the case of the > OP). Some examples for such scripts are those written to be launched > from within "su" or from "dpkg". > > > > What would you think of a cron.cf, or something similar, serving as a > > > placeholder for configuration of the default PATH and the default PATH > > > for root? > > Ech. If the policy crew decides that crond should set the path > > differently for root, then the Right Thing To Do is pick it up from > > login.defs, not create yet another place for things to be inconsistent. > > Ooch, I misunderstood the meaning of ENV_SUPATH to something related to > "su" since I found that in the su(1) manpage. Of course, the values of > login.defs should be used, you're right. > > Thanks for your time. > > [1] If you meant: > <http://lists.debian.org/debian-policy/1999/04/threads.html#00143> > which started in dd: > <http://lists.debian.org/debian-devel/1999/04/thrd2.html#00812> > -- > Loïc Minier <l...@dooz.org> > -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70
signature.asc
Description: PGP signature
