On Fri, 2008-10-17 at 09:21 -0400, Blackburn, Marvin wrote: > I am getting his message on a system that automounts some > directories. I can seem to find out what it means. > > The client is a 5.2 server and the server is a 5.2 server. Both are > running the latest updates from redhat. > > > > lookup_mount: lookup(file): key "sabayon" not found in map
It means exactly what it says, when looking for a key in a map autofs didn't find it! But, in reality there are a few problems with this. autofs is obligated to lookup any access to a directory within an automount managed directory where it's just an application with invalid entries in it's path or some other equally innocuous access. There isn't any way for it to know, if the kernel send a request, that it isn't valid. But, you may also see messages that are totally wrong and shouldn't be there at all and you might think that we should be able to detect this a bit better than we do in the kernel. The completely wrong messages are probably due to a bug (which should be fixed in the next release) and we've tried to detect invalid accesses before they're passed up from the kernel but it isn't straight forward to pick these, so we'll just have to see how the next release goes. But, why even log the messages? Because someone logged as bug complaining they were having trouble working out when mount fails were due to a missing key! > > > > Can anyone illuminate me on what this means? > > > > _____________________________________ > "He's no failure. He's not dead yet." > William Lloyd George > > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
