This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Is this possibly an issue with the type of filesystem where my application lives, or is there some sort kernel reconfiguration I need to do? I was missing CONFIG_RELAY, and CONFIG_DEBUG_FS from my kernel configuration, so are there any other things that SystemTap needs that I might be missing (I have CONFIG_KPROBES=y, and CONFIG_DEBUG_INFO=y)The function capsetp should be used with care. It exists, primar- ily, to overcome a lack of support for capabilities in any of the filesystems supported by Linux. The semantics of this function may change as it is better understood. Please note, by default, the only processes that have CAP_SETPCAP available to them are processes started as a kernel-thread. (Typically this includes init(8), kflushd and kswapd). You will need to recompile the ker- nel to modify this default.
-- Dave Nomura LTC Linux Power Toolchain
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |