I had an interesting call from a customer this morning - he was resizing some files, making them Dynamic using the command "RESIZE FILENAME 30 * *" (normally you wouldn't enter the "* *" after 30) But then his session was comsuming all of the CPU for over 20 minutes (until I killed it). Just curious if anyone knows what the system was trying to do?
We resized using the correct command format and everything is fine. The files in question were type 18, empty and very small modulo 11. Thanks, Mark Uv 10 Windows ****************************************************************************** This email and any files transmitted with it are confidential and may be subject to copyright. They are intended solely for the use of the individual or entity to which they are addressed. If you have received this message in error please notify AFS immediately by return email. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of AFS, except where an authorized sender specifically states them to be the views of AFS. It is your responsibility to verify this email and any attachments for the presence of viruses. AFS accepts no liability for any damage caused by any virus transmitted. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
