From: Giuseppe Galeota <giuseppegaleota@libero.it>
To: dccp@vger.kernel.org
Subject: Re: Monitoring DCCP: modprobe dccp_probe
Date: Thu, 29 May 2008 11:54:22 +0000 [thread overview]
Message-ID: <483E996E.7090907@libero.it> (raw)
In-Reply-To: <483D424F.5020307@libero.it>
Hi,
I have resolved.
The problem was that the "kernel debugging" in the .config file wasn't
active.
Now, I can see 'DCCP connection probing' inside Networking-->Networking
options -> The DCCP Protocol.
Thank you,
Giuseppe
Gerrit Renker ha scritto:
> Quoting Giuseppe Galeota:
>
>> Under General Setup I haven't found Kprobes, but I found Kprobes inside Instrumentation Support, and it is already active.
>> About DCCP I can see only:
>> Networking->Networking support->THE DCCP protocol->DCCP CCIDs
>> configurations-->CCID2/3 debugging messages, that are already active,
>> while I haven't found 'DCCP connection probing'.
>>
>>
> This means that the dependency for dccp_probe is not satisfied.
> The only other dependency of dccp_probe is CONFIG_PROC_FS, but this is
> not normally off. Maybe if you are using non-x86 hardware there is a
> problem with kprobes?
>
> Alternatively, if you do a
>
> grep CONFIG_NET_DCCPPROBE .config
>
> you should be getting a CONFIG_NET_DCCPPROBE=m (`y' also apparently works).
> If it is not set then check if PROC_FS is on, if not then the source is
> somewhere else.
> .
>
>
next prev parent reply other threads:[~2008-05-29 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 11:30 Monitoring DCCP: modprobe dccp_probe Giuseppe Galeota
2008-05-28 11:44 ` Gerrit Renker
2008-05-28 12:17 ` Giuseppe Galeota
2008-05-28 12:38 ` Gerrit Renker
2008-05-28 12:50 ` Leandro Sales
2008-05-28 13:12 ` Giuseppe Galeota
2008-05-28 14:07 ` Gerrit Renker
2008-05-28 14:17 ` Arnaldo Carvalho de Melo
2008-05-28 15:56 ` Gerrit Renker
2008-05-29 11:54 ` Giuseppe Galeota [this message]
2008-05-29 23:47 ` Leandro Sales
2008-05-30 8:35 ` Gerrit Renker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=483E996E.7090907@libero.it \
--to=giuseppegaleota@libero.it \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.