Ola Lundqvist wrote: > Thanks for the patch. However I think it will only work with bash, and > cron-apt uses /bin/sh as shell. Or do other shells handle $(()) ?
Using $(( expression )) is okay for POSIX shells and /bin/sh. Here is a documentation pointer. http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_04 > Do you also need as much as 10MB in /tmp? I disagree with the premise behind this however. I think trying to predict the space needed is not the best way. I think if /tmp is full and the output cannot be written that that problem should be treated as an error and reported at the point that the output cannot be written. I would much rather see something such as that instead of trying to guess at how much space is needed. Setting an arbitrary size will always be incorrect. The question I have is what should be done when a failure is noted. If the script can simply exit with an error then setting 'set -e' might be the simplest way to address this issue. It would take careful review to ensure that the script is ready for that though. Personally I prefer to check each command as it goes. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
