>> Um, why would anything quota-related ever cause errors from lseek? > Because he applies quotas to file length. The lseek is what will > take you over quota, whether you ever write or not.
At least in my experience, lseek never affects any file's size. lseek such that the file pointer is left past EOF sets it up so a write will extend the file (with a hole, if far enough past EOF and holes are supported), but the lseek itself shouldn't do anything to file size. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML [email protected] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
