dead lock not dead look. again ive read some compukter science hypertexts and found no reasonable answer to the "dead" word background. when you hear en-shit-tification, its clear what "shit" means in there, but what "dead" means in deadlock?the answer came from practice, as usual. ive been syncing 2 processes and set a timeout when the master (one) kills the slave (another), because why not, when it doesnt respond in time, thats logical. so one kills another and another is "dead" but it had the time to acquire the lock but never released it (termination doesnt run through PHP shutdown handlers), so that lock is dead, a deadlock. the first spins forever trying to get it but it will never get it.also i get why Go choose to avoid locks - locks always cause deadlocks under certain conditions
