Skip to contentSkip to conversation

determining which process triggered an automount

DISCUSSION Chris Walker 4 participants 5 messages Apr 11, 2007 – Apr 13, 2007 Kernel automounter

lore
Share & tools
lore
#0 lore raw

I'd like to determine which process triggered an automount. Might I have to use Systemtap or some other tool to determine this?

I'm on Fedora Core 5.

Thanks,

Signature · 5 lines
Chris Walker
Render Pipeline Group
Pixar Animation Studios
510/922.3736
[email protected]
maintainer
#1 lore raw
Quoted 2 lines · Chris Walker

I'd like to determine which process triggered an automount. Might I have to use Systemtap or some other tool to determine this?

Can't really do that with autofs version 4.
It's a bit of information that the daemon doesn't get in the request packet from the kernel. This information is passed to the daemon in autofs version 5 and is logged when debug logging is enabled so you could try that.

Sorry I can't be more help.
Ian

#2 lore raw
Quoted 4 lines · Ian Kent
Quoted 2 lines · Chris Walker

I'd like to determine which process triggered an automount. Might I have to use Systemtap or some other tool to determine this?

Quoted 8 lines

Can't really do that with autofs version 4.
It's a bit of information that the daemon doesn't get in the request packet from the kernel. This information is passed to the daemon in autofs version 5 and is logged when debug logging is enabled so you could try that.

Sorry I can't be more help.
Ian

I think a system tap module could get you this, but it will take some time investment for you to find out how to use it.

http://sourceware.org/systemtap/

-Peter

Signature · 3 lines
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.
#3 lore raw
Quoted 5 lines · Peter C. Norton

I think a system tap module could get you this, but it will take some time investment for you to find out how to use it.

http://sourceware.org/systemtap/

And it also takes a bit of time to find probe points that have not been optimized away, auto-inlined, etc. In any case, here's a working (in FC5) probe that will tell you who requested a directory. It could be improved to provide a full path, but I'm satisfied by it as is.

probe module("autofs4").function("autofs4_find_wait") {
	printf("%s(%d) requested %s\n", execname(), pid(),
		kernel_string($name))
}

The output is:

$ sudo stap autofs4_notify_daemon.stap
bash(5913) requested foobar
bash(5913) requested foobar
bash(5913) requested foobar
...

Maybe autofs4_find_wait is not the best place, but it works, and I found the more obvious autofs4_notify_daemon to be auto-inlined.

Hope this helps!
Fábio

Signature · 1 line
ex sed lex awk yacc, e pluribus unix, amem
#4 lore raw

This is *exactly* what I wanted. I tried it out and it works great. Thanks.

From fleite:

Quoted 37 lines · Peter C. Norton
Quoted 5 lines

I think a system tap module could get you this, but it will take some time investment for you to find out how to use it.

http://sourceware.org/systemtap/

And it also takes a bit of time to find probe points that have not been optimized away, auto-inlined, etc. In any case, here's a working (in FC5) probe that will tell you who requested a directory. It could be improved to provide a full path, but I'm satisfied by it as is.

probe module("autofs4").function("autofs4_find_wait") {
	printf("%s(%d) requested %s\n", execname(), pid(),
		kernel_string($name))
}

The output is:

$ sudo stap autofs4_notify_daemon.stap
bash(5913) requested foobar
bash(5913) requested foobar
bash(5913) requested foobar
...

Maybe autofs4_find_wait is not the best place, but it works, and I found the more obvious autofs4_notify_daemon to be auto-inlined.

Hope this helps!
Fábio

Signature · 6 lines
ex sed lex awk yacc, e pluribus unix, amem

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs
Signature · 5 lines
Chris Walker
Render Pipeline Group
Pixar Animation Studios
510/922.3736
[email protected]