Hi On Sun, Jul 29, 2007 at 02:37:25AM -0600, Bob Proulx wrote: > 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
Really good to know! Thanks. > > 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. True. > 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. I think I change this so that it shecks that there are any free space on the device, or actually that free space is > configurable value. This way the admin can choose this value, which is better than hard coded. But I agree that we should check each command in most cases. Best regards, // Ola > Bob > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]