>> ... when I tested it on my 12.04 desktop box, /proc/self/auxv had permissions
>> set to -r-------- (400) with the user and group set t whoever is logged in at the time.
Well, /proc/self always links to the current process's /proc entry. It is just a short hand
for /proc/PID, where PID is the return from getpid(), or in most shells, the value of $$.
So I would have expected any virtualbox process to be able to read its own /proc/self/auxv,
as that special file would be owned by itself (and as you noticed, has permissions set to
allow the file owner to read it.)
It remains a mystery to me that a virtualbox process often can't read this auxv file.
>> ... when I tested it on my 12.04 desktop box, /proc/self/auxv had permissions
>> set to -r-------- (400) with the user and group set t whoever is logged in at the time.
Well, /proc/self always links to the current process's /proc entry. It is just a short hand
for /proc/PID, where PID is the return from getpid(), or in most shells, the value of $$.
So I would have expected any virtualbox process to be able to read its own /proc/self/auxv,
as that special file would be owned by itself (and as you noticed, has permissions set to
allow the file owner to read it.)
It remains a mystery to me that a virtualbox process often can't read this auxv file.