Smart is in the eyes of the beholder. (huh?) I just went through a similar situation. Let's say the CREATE.FILE points to an undesirable path via some programmatic glitch. Now delete, clear, or write over the data. Anything in there goes away or gets butchered. If you use sudo to get into U2 or you are otherwise using permissions that allow you to blow away something that you really needed, you're in a world of hurt. A prompt might be nice but it should not be exposed to end-users. A mis-used Force option could be very dangerous. Be careful about what you ask for, you might get it. :)
T Susan Joslyn wrote: > The CREATE.FILE could be smart enough to recognize these latter two > situations and rectify them: > CREATE.FILE finds a VOC but no underlying file - delete the VOC and > create fresh. > CREATE.FILE finds an underlying file but no VOC pointer - create > the VOC pointer to the existing file. > > Ideally it will stop and report what is happening and ask, but there > could be a FORCE type option that did not stop for the question. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
