9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot via aan from fileserver?
Date: Sat, 31 Jan 2004 17:44:36 +0100	[thread overview]
Message-ID: <200401311644.i0VGiah20241@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Sat, 31 Jan 2004 12:03:14 +0100." <200401311103.i0VB3F518364@zamenhof.cs.utwente.nl>

Just for those interested:
> In the mean time, after being away for a day, I find at home that
> my connection has been down long enough such that a machine
> booted 'normally' from the work fs gives the 'i/o on hungup channel'
> whereas the 'tcpaan' booted one does not complain but simply
> hangs and waits -- seems what I'm doing does not (yet?) give
> me what I'm looking for...

After thinking about the code of aan.c I supected that the syslog(0, ...)
calls in the if(dialstring) branch of reconnect() were
causing the problems:
network problem -> pending connection to fs -> trying to consult
fs to see if we can write to a log file not possible ->
deadlock while waiting for the result of the log file existence test?!?

Experiments seem to confirm this -- replacing those calls to
syslog(0, Logname, ...) by calls to dmessage(0, ...)
seems to have solved the problem.

Now my only remaining problem is to make a number of connections to u9fs
reliable as well. Since there is no unix aan, easiest trick seems
to mount them all on the cpu server (where I mount them anyway)
and reexport from there.
If there were something like aan for unix, I could maybe even mount
those u9fs things on the cpu server via /lib/namespace.$sysname
(and then on the terminal at home in the same way)

Axel.


      reply	other threads:[~2004-01-31 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 13:49 Axel Belinfante
2004-01-25 13:57 ` David Presotto
2004-01-26  8:19   ` Fco.J.Ballesteros
2004-01-29 23:27     ` Axel Belinfante
2004-01-30  7:39       ` Fco.J.Ballesteros
2004-01-31 11:03         ` Axel Belinfante
2004-01-31 16:44           ` Axel Belinfante [this message]

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=200401311644.i0VGiah20241@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --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).