Amar Tumballi <amarts@xxxxxxxxxx> wrote: > This log is not a 'error', but warning. What that means is, this > condition need not be causing the error seen by the user. But the warning is followed by return ENOENT. This is why I suspected it to be related with bug where existing files sometime get ENOENT when accessed. Is the ENOENT returned after the warning ignored somewhere else? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx
