[6105] in Release_7.7_team
Re: Reworking liblocker
daemon@ATHENA.MIT.EDU (Evan Broder)
Wed Dec 3 16:56:11 2008
Message-ID: <4936FFF7.2020305@mit.edu>
Date: Wed, 03 Dec 2008 16:53:59 -0500
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: Ken Raeburn <raeburn@mit.edu>
CC: Greg Price <price@mit.edu>, release-team@mit.edu, athena10@mit.edu
In-Reply-To: <BBF43488-C5EB-4689-B6F3-C4B2AF2B5E96@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Flag: NO
X-Spam-Score: 0.00
Ken Raeburn wrote:
> Is it known that all the file system entries in Hesiod that mount
> under /mit attach at /mit/<lockername> and not elsewhere? I know it
> didn't used to be the case, but the one example I know of (emacsdev)
> seems to have been fixed, probably long ago.
These days there are very, very few lockers that don't mount at
/mit/<lockername> - oracle8 is the big example I know of.
> Does the automounter support filesystem names of the form
> 'foo@raeburn.org' like attach does?
I'm going to start by taking a moment to boggle at that. That's awesome
- I had no idea Hesiod did that.
In any case, what currently happens with these lockers is that they get
mounted at /mit/<lockername> regardless of whether they should or not. So...
remus:~ evan$ ls -ld /mit/emacs@raeburn.org
lrwxrwxrwx 1 root root 30 1969-12-31 19:00 /mit/emacs@raeburn.org ->
/afs/raeburn.org/project/emacs
I think I'm in favor of forcing lockername to mount at /mit/lockername
always, but I could possibly be swayed.
Are there justifications for keeping the ability to mount lockername at
not-/mit/lockername other than that being the way it's always been done.
Also, could someone tabulate what lockers still in Moira don't mount at
/mit/lockername? I, uh, tried, but managed to trigger "MOIRA moirad on
MOIRA6.MIT.EDU: attempted query with too many rows"
- Evan
