Hi Tom Thank you very much for your answer.
I'd advise against commenting out the line. What happens if someone > installs the > executable at a later date? > > A common solution is to test to see if the command exists and only run > it if it does. > > [th199096 at warlock ~]> sudo crontab -l | grep "\-x" > 30 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/gsscred_clean > 1 2 * * * [ -x /usr/sbin/rtc ] && /usr/sbin/rtc -c > /dev/null 2>&1 So, we could put in code the same thing as the suggested workaround. But, could we consider it valid for any executable programmed in the crontab? In case it be valid, do we need to implement a kind of notification for this situation? Thanks, > Tom > > > PS: I'll be willing to sponsor you once you have a fix ready.... Thanks a lot!. I will be working on it, and I will be posting you. Regards. Sergio.
