From: "Alberto Cortés" <alcortes@it.uc3m.es>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] snoopy thinks that the cpu command talks 9p
Date: Tue, 16 Jan 2007 12:59:00 +0100 [thread overview]
Message-ID: <20070116115900.GA16784@it.uc3m.es> (raw)
Hello.
Trying to understand how authentication works, I ended up using
snoopy on a cpu connection, something like:
% snoopy -f 'tcp(sd=17010)'
and, on another window:
% cpu
This will give you lots of lines that looks like:
ninep(68656c6c6f203966616e7321)
I believe it should say something like:
unknown(68656c6c6f203966616e7321)
or
unknown"helo 9fans"
Maybe this brings up again the topic of dynamic loading of
modules.
--
Alberto Cortés
next reply other threads:[~2007-01-16 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 11:59 Alberto Cortés [this message]
2007-01-16 12:18 ` Russ Cox
2007-01-16 13:08 ` Alberto Cortés
2007-01-16 13:42 ` Russ Cox
2007-01-16 14:05 ` Alberto Cortés
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=20070116115900.GA16784@it.uc3m.es \
--to=alcortes@it.uc3m.es \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).