From: Stef B. <st...@bo...> - 2008-03-09 11:45:11
|
Hello, now I can check the flow of what happens (by activating debugging). It's much more clear now. But when I look at query_inode_full, I do not understand what happens there at all. The purpose of this function is to translate a path into a inode, right? But it does much more things. It "returns" a table nlinks, the inode, the parent. (and more?) Can someone explain why this is? It runs complicated queries.... Thanks in advance, Stef Bon |