Luck, Tony wrote: >>Well, this printk had been suggested by somebody (sorry I don't remember >>who) when I first submitted the patch. Actually I think it might be >>useful for a sysadmin to be aware of a change in the msgmni value: we >>have the message not only at boot time, but also each time msgmni is >>recomputed because of a change in the amount of memory. > > > If the message is directed at the system administrator, then it would > be nice if there were some more meaningful way to show the namespace > that is affected than just printing the hex address of the kernel structure. > > As the sysadmin for my test systems, printing the hex address is mildly > annoying ... I now have to add a new case to my scripts that look at > dmesg output for unusual activity. > > Is there some better "name for a namespace" than the address? Perhaps > the process id of the process that instantiated the namespace??? >
Unfortunately no when we are inside an ipc namespace, we don't have such interesting informations. But I agree with you, an address is not readable enough. I'll try to find a solution. Regards, Nadia _______________________________________________ Containers mailing list [EMAIL PROTECTED] https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list [email protected] https://openvz.org/mailman/listinfo/devel
