C
ChUIMonster
Guest
Guilt is in the eye of the beholder. It might be that some particular user grabs a whole mess of locks *and* blows up -L. Or some user grabs a lot, but not all of the locks and the normal workload results in some poor unlucky user just happens to ask for a modest helping at just the wrong moment. Or maybe -L is simply too small and a bunch of users with perfectly reasonable requirements all make requests at about the same time... Having said that... I've been know to go tripping through _userlock like so: for each _userLock no-lock where _userLock-usr ? and _userLock-recid[512] ?: to find people that seem to have more locks than might be generally recognized as "reasonable"... I find the approach above to be *much* safer than fiddling with _lock.
Continue reading...
Continue reading...