On Sat, 29 Jan 2005, Pavel Troller wrote:
On Wed, 26 Jan 2005, Pavel Troller wrote:
But you leave out the crucial log trace following the mount?
Can we see more of what follows here please.
IanHello Ian, OK, I'm sending the full system log during the mount/umount... I don't know which part You are interested in, but I don't see anything special...
Maybe because what I'm looking for is not there. So this is probably the cause of the probem.
I think that what is happening is that for the short timeouts you are using the expire timer is being set to 0, disabling expiration.
I'll have a look but does this work if you set the timeout to 4 seconds or above?
Hi Ian, I increased the timeout to 10 seconds for the test. No change has been observed, still no auto umount. I would like to remember that it worked perfectly and then stopped working probably after upgrading some part of this system. I'm using exactly the same setup on other computers with no problems. Timeout is set to 3 there, it was 3 here too, but I tried to change the value after it ceased to work. So definitely, it's not the cause. The only bigger change I remember I did was upgrading bash to 3.0. But I cannot imagine how could changing a shell cause such a problem. I even tried to put the old bash back and test it and it didn't work too. Please tell me where to put some debug texts to be logged or so, I can modify the source and cooperate with finding the bug.
What I'm looking for is log entries after the mount happens.
Where you see the alarm firing and expire checks happening.
Basically, you don't have any expiration happening (obviously) so the alarm timer must be set to 0. We need to establish why.
So using the --debug should give you that.
Include the log from each test please and I'll put together a patch to log some extra stuff.
I'll go back through you mails to check what version your using.
Ian
_______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
