FS#35826 - [cronie] /etc/cron.d/0hourly usePATHthatuse sbin locations
Attached to Project:
Arch Linux
Opened by Pablo Lezaeta (Jristz) - Sunday, 16 June 2013, 23:42 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 23 June 2013, 09:33 GMT
Opened by Pablo Lezaeta (Jristz) - Sunday, 16 June 2013, 23:42 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 23 June 2013, 09:33 GMT
|
Details
Description:
whit themove of all to usr/bin and the move of all PATHs to point that (alongside usr/local/) this file owned by cronieremain using the old paths SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin Ithink for concistency whit Arch decicionis needed to fix that SEHLL and PATH to point only to the needed places (/usr/bin/bash and /usr/bin) this grant concistency and prebent future problems Additional info: * cronie 1.4.9-4 Steps to reproduce: less /etc/cron.d/0hourly pacman -Qo /etc/cron.d/0hourly which bash less /etc/profile | grep PATH now compare SHELL and PATHs |
This task depends upon
Closed by Gaetan Bisson (vesath)
Sunday, 23 June 2013, 09:33 GMT
Reason for closing: Won't implement
Additional comments about closing: cronie-1.4.9-5 in [testing]
Sunday, 23 June 2013, 09:33 GMT
Reason for closing: Won't implement
Additional comments about closing: cronie-1.4.9-5 in [testing]
and I think (not sure if 100% correctly) a sed command that change the path can by enough, none abouth patch
but yes SHELLcan by (for now) ok, but PATH is redundant and as was mentioning on the mailistin (the public one) for example many paths was changed to a simply (/usr/local/sbin:/usr/local/bin:/usr/bin) and no more
PATH is indeed redundant but that's not worth fixing in my opinion.
the #!/bin/bash issue ca by changed when the links goig to be removed
in resume: fix only PATH in trunk whit a sed
what about that?
first is redudat with the actuals simlinks
second that PATH omit usr/local an if I have my own bersion of $(programa) is omither by that script
but... why upstream not give the option to custom that path at build time and prevent patchings??
Besides, I see no point making the default PATH "fancier" in /etc/cron.d/0hourly and /etc/anacrontab while leaving it to its current value in processes spawned directly by crond. The latter uses _PATH_DEFPATH from /usr/include/paths.h which is defined to "/usr/bin:/bin" and I am not overriding that in crond's code. If _PATH_DEFPATH gets changed then I will update the aforementioned files accordingly.
In the time being, I will release a new version which adds /etc/cron.d/0hourly to the backup array, so you can customize it if you like.