Dan, Ian, Jeff:
I work at a large U.S. Government Lab and after updating some of our
Ops systems from RHEL 4 Update 4 to Update 5, all Hell broke loose
as we have been plagued by this bug ever since - we are a Sun and
Red Hat shop, and our software architecture is heavily dependent upon
lots of automounts. (I can very easily replicate it in our own
environment with a simple test script that usually provokes the
race condition in about 10-15 minutes, tops.)
I am getting the impression from the bug reports (and posts in
this thread) that this bug is *not* fixed in 2.6.9-55.0.9; and might
not be until some point in the future when 2.6.9-61 is available via
"up2date". Am I correct in that assumption?
If so, we may have little choice but to rollback to Update 4 by
doing complete reinstalls from scratch (groan). Is there any
info on when this bug first crept in, and is Update 4 - with
autofs-4.1.3-187 - safe to roll back to? The natives are restless,
and they've already shown up outside my office door with torches
and pitchforks. I've got a lot of unhappy Flight Projects reps
on my hands. We need to make a command decision here Real Soon Now.
Any illumination much appreciated.
- Greg Earle
_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs
