On Oct 5, 2017, at 11:06 PM, David Adams via 4D_Tech <[email protected]> wrote: > > * New process () / Execute on server () When they finish, they're dead. > They're supposed to release file locks, record locks, etc. If you start a > new copy of the process with the same name, it starts off in a "virginal" > state. > > Which is it for workers? I thought it was like New process(), but am seeing > evidence that it's not always the case. The docs aren't explicit. I take > the implication to be that they should be fully dead, even if started > almost instantly. But this doesn't seem to be true.
Perhaps I am misunderstanding your question. Do you mean after a worker has been killed with KILL WORKER? Workers are not like New Process/EXECUTE ON SERVER processes in that they do not die "When they finish...". To me that is the whole idea of workers. If you are asking with respect to your other issue with file locks, I hear you. I have not tested the problem, but if files. or anything else, are remaining locked after a worker is killed with KILL WORKER then indeed Houston We Have a Problem. With respect to locked files, killing a worker should have the same effect on any files locked by the worker as one would see if you restarted 4D. My guess is, unfortunately, that the unlocking files when 4D quits is managed by the OS not 4D as is would be the case with workers. John John Baughman Kailua, Hawaii (808) 262-0328 [email protected] ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
