Linux进程被视为文件,Linux下如何知道文件被那个进程写

您好，从您博客中学习到这个方法，不过木有成功呀，求助：

1. 我的inodewatch.stp在不同的目录下

/usr/share/doc/systemtap-client-1.8/examples/io/inodewatch.stp

不过内容一致，应该是不影响的吧~

内核版本：2.6.32-279.14.1.el6.x86_64

我运行“rpm -qf /usr/bin/stap”得到的结果是：

systemtap-client-1.8-7.el6.x86_64

systemtap-devel-1.8-7.el6.x86_64

2. 然后根据您用法，我在boot分区随便建一个文件，并写入内容……

然后调用stap去找到哪个进程在写该文件！报错了……

[root@test boot]# stap /usr/share/doc/systemtap-client-1.8/examples/io/inodewatch.stp 8 1 25

semantic error: while resolving probe point: identifier ‘kernel’ at /usr/share/systemtap/tapset/vfs.stp:820:19

source: probe vfs.write = kernel.function(“vfs_write”)

^

semantic error: missing x86_64 kernel/module debuginfo under ‘/lib/modules/2.6.32-279.14.1.el6.x86_64/build’

semantic error: while resolving probe point: identifier ‘vfs’ at /usr/share/doc/systemtap-client-1.8/examples/io/inodewatch.stp:3:7

source: probe vfs.write, vfs.read

^

semantic error: no match

semantic error: while resolving probe point: identifier ‘kernel’ at /usr/share/systemtap/tapset/vfs.stp:752:18

source: probe vfs.read = kernel.function(“vfs_read”)

^

semantic error: while resolving probe point: identifier ‘vfs’ at /usr/share/doc/systemtap-client-1.8/examples/io/inodewatch.stp:3:18

source: probe vfs.write, vfs.read

^

Pass 2: analysis failed. Try again with another ‘–vp 01′ option.

Missing separate debuginfos, use: debuginfo-install kernel-2.6.32-279.14.1.el6.x86_64

正在http://sourceware.org/systemtap/ 继续学习中……

求指导: lin_credible@163.com. 或者直接回复，万分感谢~~

[Reply]

Yu Feng Reply:

June 27th, 2013 at 11:51 am

系统的符号信息没安装好。