From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] pnp factotum from linux to plan 9: site-specific password failures.
Date: Wed, 28 May 2008 10:37:38 -0400 [thread overview]
Message-ID: <20080528143620.F3EC31E8C84@holo.morphisms.net> (raw)
In-Reply-To: <13426df10805270838hf4ffcc0o671e9d6c53f3a3d3@mail.gmail.com>
> run and get same problem.
Factotum provides a log file that was intended to be
a list of interesting events. While the log file was
implemented, nothing was being logged to it.
I have added log statements tracing the important
events in factotum and p9sk1 in particular.
cd $PLAN9/src/cmd/auth/factotum
cvs up # or hg pull -u
mk install
Then restart your factotum, and run drawterm and
"9p read factotum/log" in separate windows.
You'll have to interrupt "9p read" when you're done,
since it blocks waiting for more log messages.
Russ
next prev parent reply other threads:[~2008-05-28 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 15:06 ron minnich
2008-05-27 15:14 ` Russ Cox
2008-05-27 15:38 ` ron minnich
2008-05-28 14:37 ` Russ Cox [this message]
2008-06-04 17:14 ` ron minnich
2008-06-04 17:33 ` Russ Cox
2008-06-16 15:50 ` ron minnich
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=20080528143620.F3EC31E8C84@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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).