severity 617898 normal thanks Hi,
Recently I added a logrotate setup that was very similar to apache2's, but I ran it from a cron.d file, and it obviously failed because the normal logrotate runs from /etc/crontab, which has a different PATH set. I think this is not a wishlist item to change this, rather it is a genuine bug, because I don't see the actual rationale for the behavior of /etc/crontab and cron(8) to differ in such a fundamental way, and it's clearly causing a number of users to have to amend their cron.d files in a way that is redundant and error-prone (having to redefine PATH everywhere reminds me of the dark days of 1990s Unix systems, and it is NOT something we want to replicate ever again). I certainly don't see a downside with adding the sbin variants, because on Debian systems they're expected to be as reliable as bin variants, and there should be no confusing overlaps. For local, an argument could be made that it exposes a possibility of problems with random local binaries getting in the way, but it would still probably be better to do this kind of a transition to get everything consistent. Random complexity just leads to more trouble. Please fix this. TIA. -- Josip Rodin
