fyi, I've been trying to reproduce this in 2.6.18, but haven't been able to. The vserver developers believe the bug wasn't actually introduced until 2.6.19. So, our patch in -12 was likely unnecessary. -- dann frazier | HP Open Source and Linux Organization