Julian, On Friday 20 October 2006 15:13, Boyan Tabakov wrote:
On 21.10.2006 00:49, Julián Rodríguez Bajo wrote:
Thanks Randall, and thanks Boyan. Is there any way to know which process opens the file in a wrong way? I have tried with lsof and fuser, but the information reported does not seem to show open mode.
I don't know for sure, but I think there is no easy way. Of course you could always search through the sources:)
Were we not on Linux, it would be possible using the "+fg" option: -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- "The listing of information from kernel file structures, requested with the +f [cfgGn] option form, is normally inhibited, and is not available for some dialects - e.g., /proc-based Linux. When the prefix to f is a plus sign (`+'), these characters request file structure information: c file structure use count f file structure address g file flag abbreviations G file flags in hexadecimal n file structure node address ... "FILE-FLAG when g or G has been specified to +f, this field contains the contents of the f_flag[s] member of the kernel file structure and the kernel's per-process open file flags (if available); `G' causes them to be displayed in hexadecimal; `g', as short-hand names; ...: AIO asynchronous I/O (e.g., FAIO) AP append ... [ and many more ] " -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- Note especially: "... is not available for some dialects - e.g., /proc-based Linux." Randall Schulz