On Sun, 2009-04-26 at 13:39 +0000, Alexander Gieg wrote:
> Public bug reported:
>
> Binary package hint: consolekit
>
> This line appears in my syslog. I don't know what its importance is:
>
> console-kit-daemon[2951]: WARNING: Couldn't read /proc/2950/environ:
> Failed to open file '/proc/2950/environ': No such file or directory
>
> The folder 2950 itself also doesn't exist. 2951 however does. Just a
> guess then: shouldn't it be trying to read /proc/2951/environ instead?
Nope. /proc/ is a virtual file-system that has a directory per process,
so /proc/2950 and /proc/2951 give information about different processes.
My guess is that process 2950 is very short-lived, so consolekit
notices it, and then when it goes to find the information about the
process it has already exited, so the directory no longer exists.
If that is the case then it would make this bug "Invalid" I guess, but
it would be good to confirm that it is indeed the case.
On Sun, 2009-04-26 at 13:39 +0000, Alexander Gieg wrote: kit-daemon[ 2951]: WARNING: Couldn't read /proc/2950/environ: 2950/environ' : No such file or directory
> Public bug reported:
>
> Binary package hint: consolekit
>
> This line appears in my syslog. I don't know what its importance is:
>
> console-
> Failed to open file '/proc/
>
> The folder 2950 itself also doesn't exist. 2951 however does. Just a
> guess then: shouldn't it be trying to read /proc/2951/environ instead?
Nope. /proc/ is a virtual file-system that has a directory per process,
so /proc/2950 and /proc/2951 give information about different processes.
My guess is that process 2950 is very short-lived, so consolekit
notices it, and then when it goes to find the information about the
process it has already exited, so the directory no longer exists.
If that is the case then it would make this bug "Invalid" I guess, but
it would be good to confirm that it is indeed the case.
Thanks,
James