The topic seems to have drifted from CAPTURE in UniVerse to PHANTOM in UniData.
udt does it have its own CAPTURE problem sometimes http://www.indexinfocus.com/dl/u2list/200310/57567.html but that doesn't seem to be the problem described below. PHANTOM doesn't use pid numbers for uniqueness, but it does depend on _PH_/jobname_time_date being unique, and I thought it always made the filename unique anyway, but maybe that doesn't always work right. Maybe udt is occasionally failing to resolve a race condition between 2 phantoms that are trying to create the same _PH_ file. Does anything other than your cron job start phantoms? Or could a new instance of your cron job start running while a previous instance is still running? > -----Original Message----- > From: Dan Eichholz @ @iproduction.com > > For us, the error occurs during a sequence of > unidata calls from the command line (cron) > and phantom is not involved. ****** Are you certain? Isn't something doing "PHANTOM webster" ? ****** > Our cron script runs about 30 unidata calls > sequentially on a variety of accounts. > Usually they last for less than a second. > This whole sequence repeats every 10 minutes. > We get 0 to 3 of these per day > with no consistent time > or correlation to server load. > > cat: cannot open _PH_/webster40980_14962 The information contained in this e-mail message may be privileged and confidential information and is intended only for the use of the individual and/or entity identified in the alias address of this message. If the reader of this message is not the intended recipient, or an employee or agent responsible to deliver it to the intended recipient, you are hereby requested not to distribute or copy this communication. If you have received this communication in error, please notify us immediately by telephone or return e-mail and delete the original message from your system. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
