linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Furness <paul.furness@vil.ite.mee.com>
To: linux-admin@vger.kernel.org
Subject: Re: shortcuts and AMD
Date: 15 Oct 2002 15:20:47 +0100	[thread overview]
Message-ID: <1034691647.10718.4.camel@zebra.vil.ite.mee.com> (raw)
In-Reply-To: <1034688090.1819.29.camel@zebra.vil.ite.mee.com>

Forgot to mention: I'm using bash. I did try a number of other shells
but get the same problem.


On Tue, 2002-10-15 at 14:21, Paul Furness wrote:
> Hi.
> 
> I have an ongoing problem which is really annoying. When my home dir is
> mounted using AMD, some apps report the full real path to the mount
> point, not the virtual one.
> 
> In other words, if I open a terminal window and do "pwd" I get this:
> 
> /.automount/x4/a/x4/home/paul
> 
> when I want to get this:
> 
> /home/paul
> 
> Interestingly, if I open the terminal and then do "cd" I end up where I
> expect - in /home/paul
> 
> 
> Here's a bit more tech info:
> 
> I have a server (running RH6.2) which serves home directories using NFS
> version 2.0 shares (I'm planing to migrate the servers to Redhat 7.3 and
> NFS 3 at some point soon). When I log in on a workstation, AMD
> automounts my home directory for me on the workstation concerned. There
> are varous workstation versions, but they are all either am-utils-6.0.3
> or am-utils-6.0.7. They all exhibit the problem.
> 
> The amd.conf file is more or less all defaults, and the amd.home file
> (which is shared using NIS) has just this in it:
> 
> #defaults
> /defaults      \
> opts:=rw,intr,grpid,hard,nosuid,quota,proto=udp;type:=nfs
> 
> #general users
> *       host==x4;type:=link;fs:=/a/x4/home;sublink:=${key} || \
>         rhost:=x4;rfs:=/a/x4/home;sublink:=${key}
> 
> 
> Admittedly, I didn't create this set up - it was here when I arrived,
> and I'm only just now looking at changing it. I looked at AMD docs and
> then a book about it, so I believe that the "general users" line is
> saying: If the user logs in to x4 (the server with home dirs on it) then
> make a link to their home directory in /home. Otherwise, mount it using
> NFS, but if more users log in, don't create a new mount for each of
> them; just use the one already there and link to it.
> 
> 
> This problem is actually even worse in tcsh because it reports the full
> path in the prompt (by default).
> 
> 
> Anyone seen this? Anyone know where or how to stop it happening?
> 
> 
> -- 
> Paul Furness
> 
> Systems Manager
> 
> 2+2=5 for extremely large values of 2.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
-- 
Paul Furness

Systems Manager

2+2=5 for extremely large values of 2.


  reply	other threads:[~2002-10-15 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 13:21 shortcuts and AMD Paul Furness
2002-10-15 14:20 ` Paul Furness [this message]
2002-10-15 14:34   ` shell web frontend Miguel González Castaños
2002-10-15 22:49     ` The Daemon Balrog
2002-10-16  7:13       ` terry white

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=1034691647.10718.4.camel@zebra.vil.ite.mee.com \
    --to=paul.furness@vil.ite.mee.com \
    --cc=linux-admin@vger.kernel.org \
    /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).