Adam Williamson wrote: > No, that sounds like exactly the bug discussed above, and I would bet > dollars to donuts you got an update to 'at' at the same time as you got > an update to the kernel. The 'at' update fixes the bug. Yes, that is correct. Along with the kernal was at-3.1.13-5.fc16. Thanks for the info :-)