[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Spurious 404's still there + some info



I'm still getting them and can reproduce them pretty reliable by rebooting
the machine.

My setup is so that I have symlinks in my tux rootdirectory to give more
than 1 name to the same virtual host. If I reboot the machine (with
2.4.9-ac9-tux-E7 on it) and I do requests to port 80 for one of the
symlinks I'll get 404's. Even for the real directory I get 404's. If I do
a ls of the tux rootdir I still get 404's, if I do a ls -al it stops.

The main hints are:
Sep  8 02:57:27 borneo kernel: <22667:input.c:43>: path_walk() returned with -530!
Sep  8 02:57:27 borneo kernel: <22667:input.c:43>: path_walk() returned with -2!

It is not a tux-problem but obviously further down in the kernel. For some
reason path_walk fails while it shouldn't or while we don't expect it to.
Doing ls -al which gets everything cached in memory makes path_walk work.
Maybe just calling path_walk is not reliable?

I'm not really familiar with all the code related to path_walk but I'll do
my best to dig up what I can. Help is off course greatly appreciated.

Dirk Moerenhout ///// System Administrator ///// Planet Internet NV





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []