From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] clunk clunk
Date: Tue, 3 Jan 2006 16:47:50 -0500 [thread overview]
Message-ID: <91a087f2f4440d8df784baf9a9abd2b6@plan9.bell-labs.com> (raw)
In-Reply-To: <775b8d190601031333l11782437rd6218e79f5cb3d8e@mail.gmail.com>
Instead of engaging in handbags, why don't
you demonstrate the problem and how to fix it?
--jim
On Tue Jan 3 16:34:12 EST 2006, bruce.ellis@gmail.com wrote:
> I can do anything I like Russ. A fileserver is not the size of a fridge.
> It's often a user process. If you don't think this is a problem well
> live with it. I don't like rebooting a machine that's been running for
> months because of this "bug".
>
> Mother Mary may believe your explanation but it is a BUG which
> I squashed.
>
> brucee
>
> On 1/4/06, Russ Cox <rsc@swtch.com> wrote:
> > > Bullshit. It happens all the time. Rio+Plumber is a simple example.
> >
> > In the standard profile, as set up by /sys/lib/newuser
> > or demonstrated in /usr/glenda/lib/profile,
> > plumber is run before rio starts, so rio has
> > plumber mounted but not vice versa:
> >
> > % grep plumb /proc/^`{ps|grep rio|awk '{print $2}'}^/ns
> > /proc/86746/ns:mount #s/plumb.rsc.86763 /mnt/plumb
> > /proc/86768/ns:mount #s/plumb.rsc.86763 /mnt/plumb
> > /proc/86769/ns:mount #s/plumb.rsc.86763 /mnt/plumb
> > /proc/86770/ns:mount #s/plumb.rsc.86763 /mnt/plumb
> > /proc/86771/ns:mount #s/plumb.rsc.86763 /mnt/plumb
> > /proc/86772/ns:mount #s/plumb.rsc.86763 /mnt/plumb
> > /proc/86773/ns:mount #s/plumb.rsc.86763 /mnt/plumb
> > % grep rio /proc/^`{ps|grep plumb|awk '{print $2}'}^/ns
> > %
> >
> > If you want to actually cause a loop, then you could run
> > plumber in your riostart (as in rio -i riostart) file. But there
> > are plenty of ways to shoot yourself in the foot with
> > ref count loops if you really want to go there. A much
> > more direct one is to run a file server that mounts
> > itself into its own name space.
> >
> > Russ
> >
next prev parent reply other threads:[~2006-01-03 21:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 19:28 Bruce Ellis
2006-01-03 19:38 ` Sascha Retzki
2006-01-03 19:46 ` Russ Cox
2006-01-03 20:07 ` Bruce Ellis
2006-01-03 20:24 ` Russ Cox
2006-01-03 21:33 ` Bruce Ellis
2006-01-03 21:47 ` jmk [this message]
2006-01-03 22:09 ` Bruce Ellis
2006-01-03 22:14 ` jmk
2006-01-03 22:16 ` Bruce Ellis
2006-01-03 22:36 ` Russ Cox
2006-01-03 22:45 ` Bruce Ellis
2006-01-04 12:15 ` Russ Cox
2006-01-04 12:25 ` Bruce Ellis
2006-01-04 15:36 ` Ronald G Minnich
2006-01-04 15:41 ` Bruce Ellis
2006-01-05 9:36 ` Francisco J Ballesteros
2006-01-05 9:39 ` Russ Cox
2006-01-05 12:00 ` Bruce Ellis
2006-01-05 12:36 ` Charles Forsyth
2006-01-05 15:26 ` Francisco J Ballesteros
2006-01-06 21:34 ` Dave Eckhardt
2006-01-06 21:57 ` Bruce Ellis
2006-01-06 22:00 ` Francisco J Ballesteros
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=91a087f2f4440d8df784baf9a9abd2b6@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--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).