Hi, Hmm, wouldn't correct solution be something like this: when server boots up, vserver utilities report to the kernel the inode number of vservers directory ( and possibly minor&major number of device on which it's sitting ), and the vserver barrier becomes checking the inode instead of some special-case of various volatile settings? That would require small change in userspace, but wouldn't it be worth the trouble?
If so, what would be correct way to send vserver inode to kernel? echo "1245334" > /proc/sys/verver-inode ? -- Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 ..The program fails and the power plant explodes, poisoning the earth and the sea. Famine and disease sweep the world. All die. Oh, the embarrassment. _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
