tag 297572 confimed hi bill,
thanks for the info. looks like this problem does indeed exist. the question is: is it really a bug? the software seems to execute just fine (although after a slight delay until the kernel spits back ELOOP). is this normal/reasonable behavior, or should the devs go through the effort to manually detect this situation? seems unnecessary since its already handled. mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
