This is a discussion on name cache in kdb within the AIX Operating System forums, part of the Unix Operating Systems category; --> Hello, There is a 'dnlc' command in AIX inside kdb. I see that it prints a really huge list ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, There is a 'dnlc' command in AIX inside kdb. I see that it prints a really huge list -the last entry of which is ..init.state. Is that really the end of name cache or is there some other marker to indicate end of name cache? I can see some entries with vnode# = 0x0. How can that be a valid entry and if it isn't why is it in the name cache? Is this a bug or a feature? I would appreciate any tips on understanding the output of dnlc. thanks -kamal |
| ||||
| I may not have written correctly in the post below -but I am interested in the manpage for 'dnlc' command in kdb. I found another post which claims that IBM makes it a pt not to provide access to the namecache. http://groups.google.co.in/group/bio...02fa f18c2f32 I wish IBM could explain to its customers why they have given a 'dnlc' command in kdb -but refused to document its output. Is it intentional or accidental?? regards -kamal Kamal R. Prasad wrote: > Hello, > > There is a 'dnlc' command in AIX inside kdb. > I see that it prints a really huge list -the last entry of which is > .init.state. Is that really the end of name cache or is there some > other marker to indicate end of name cache? I can see some entries with > vnode# = 0x0. How can that be a valid entry and if it isn't why is it > in the name cache? Is this a bug or a feature? > > I would appreciate any tips on understanding the output of dnlc. > > thanks > -kamal |