Hi Masatake,
On Tue, Jul 24, 2012 at 10:08:31PM +0900, Masatake YAMATO wrote:
> (I have got no reply since 11th Jul. So I resend this mail here.
> Please, review this patch and merge it if no problem.)
>
> (The patch sets are rebased to bluetooth-next. Unnecessary white
> spaces are trimmed.)
(I have got no reply since 11th Jul. So I resend this mail here.
Please, review this patch and merge it if no problem.)
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
lsof command can tell the type of socket processes are using.
Internal lsof uses inode
(I have got no reply since 11th Jul. So I resend this mail here.
Please, review this patch and merge it if no problem.)
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
lsof command can tell the type of socket processes are using.
Internal lsof uses inode
Hi Masatake,
On Tue, Jul 24, 2012 at 10:08:31PM +0900, Masatake YAMATO wrote:
(I have got no reply since 11th Jul. So I resend this mail here.
Please, review this patch and merge it if no problem.)
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
Hi Masatake,
On Wed, Jul 11, 2012 at 09:19:06PM +0900, Masatake YAMATO wrote:
> > I've tested the patch and it creates entries in /proc/net
>
> Thanks.
>
> > BTW: Shall lsof be able to identify l2cap protocol?
> >
> > for l2test it prints: "can't identify protocol"
>
> No. I'll work on lsof
Hi Masatake,
On Wed, Jul 11, 2012 at 09:19:06PM +0900, Masatake YAMATO wrote:
I've tested the patch and it creates entries in /proc/net
Thanks.
BTW: Shall lsof be able to identify l2cap protocol?
for l2test it prints: can't identify protocol
No. I'll work on lsof side after the
Hi,
> Hi Masatake,
>
> On Wed, Jul 11, 2012 at 01:58:31PM +0900, Masatake YAMATO wrote:
>> (The patch sets are rebased to bluetooth-next. Unnecessary white
>> spaces are trimmed.)
>>
>> lsof command can tell the type of socket processes are using.
>> Internal lsof uses inode numbers on socket
Hi Masatake,
On Wed, Jul 11, 2012 at 01:58:31PM +0900, Masatake YAMATO wrote:
> (The patch sets are rebased to bluetooth-next. Unnecessary white
> spaces are trimmed.)
>
> lsof command can tell the type of socket processes are using.
> Internal lsof uses inode numbers on socket fs to resolve the
Hi Masatake,
On Wed, Jul 11, 2012 at 01:58:31PM +0900, Masatake YAMATO wrote:
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
lsof command can tell the type of socket processes are using.
Internal lsof uses inode numbers on socket fs to resolve the type
Hi,
Hi Masatake,
On Wed, Jul 11, 2012 at 01:58:31PM +0900, Masatake YAMATO wrote:
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
lsof command can tell the type of socket processes are using.
Internal lsof uses inode numbers on socket fs to resolve
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
lsof command can tell the type of socket processes are using.
Internal lsof uses inode numbers on socket fs to resolve the type of
sockets. Files under /proc/net/, such as tcp, udp, unix, etc provides
such inode
(The patch sets are rebased to bluetooth-next. Unnecessary white
spaces are trimmed.)
lsof command can tell the type of socket processes are using.
Internal lsof uses inode numbers on socket fs to resolve the type of
sockets. Files under /proc/net/, such as tcp, udp, unix, etc provides
such inode
12 matches
Mail list logo
