On Sep 23, 10:59, Raymond Brennan wrote:
Subject: RE: Soft Links ON NT ( again) Mark,
I've got a quota tree on my F520 called "sandbox". My F520 system name is "tap", mainly because I got fed up of typing in "netapp" all the time. Anyway, what I'm trying to do is to get soft links with absolute path names to work on NT. They work fine on Unix(as you woud expect). I've installed SecureShare on all my PCs and am using Unix-style security on "sandbox" and indeed as the default security style on all other trees.
I use NIS on my LAN. "sandbox" on "tap" is accessed on Unix as /eeg/sandbox-the NIS map is called auto.eeg and has this line in it :
sandbox -intr tap:/sandbox
So, on Unix, all I have to do is
# cd /eeg/sandbox
and I'm there. Hard links (ln file linkname) work fine on NT, as do relative soft links ( ln -s ../file linkname). The problem I'm having is with soft links with absolute path names on NT. If, for example, I do # cd /eeg/sandbox/dir2 # ln -s /eeg/sandbox/dir1/file linkname
NT can't seem to access linkname on /eeg/sandbox/dir2 at all, apart from showing it in the Windows Explorer. I hope this is clear.
My /etc/symlink.translations file looks like this :
Map /sandbox/* //sandbox/*
The double slash on the second field is to counteract Bud ID 9553, which I found on the NOW website. Also, I've tried terminating and restarting CIFS, but without success.
Thanks for any help you can give me.
I think I know why the NT box is having problems, and I think I can demonstrate a similar situation on two Unix boxes.
Simply put, absolute symlinks have too much information, they're too precise for either the NT box or the filer to map them correctly.
To demonstrate my hypothetical scenario, I've use my home directory on ukwfs2 another F520 (running 4.3.1, for interest).
On our (SunOS4.1.4) admin host:
uk-dns-stv1-root /net/ukwfs2/users/d23/mds46523: ln -s \ /net/ukwfs2/users/d23/mds46523/dead.letter flibble
uk-dns-stv1-root /net/ukwfs2/users/d23/mds46523: ln -s ./dead.letter flobble
Creating two symlinks in my home directory to a simple text-file also in the directory, one absolute, one relative.
Now, on a client, in my home directory:
0 ukwit12> head -2 flibble UX:head: ERROR: Cannot read from flibble 1 ukwit12> head -2 flobble
From mds46523 Thu Sep 17 18:07:40 1998
From: mds46523@ukwsv1.ggr.co.uk (Simmons Mr M D)
The absolute symlink simply overspecifies the location, which my client has no way to map to something it can understand and use.
The NT box is in as bad a position as my Unix client - the /eeg/... part of any absolute symlink in your Unix domain doesn't match anything in the NT box's wordlview, and the filer has no rule to map it for the NT box.
Extend the mapping rules in the filer, or revert all absolute symlinks to relative symlinks and I think you'll be able to work around the problem.
I'd try adding:
Map /eeg/sandbox/* //sandbox/*
to your /etc/symlink.translations file.
:)
"What do people mean when they say the computer went down on them?"
--Marilyn Pittman
-----Original Message----- From: Mark Muhlestein [mailto:mmm@netapp.com] Sent: Tuesday, September 22, 1998 6:40 PM To: Raymond Brennan Subject: Re: Soft Links ON NT ( again)
Send me a copy of your symlink.translations file, along with a specific description of what you are trying to do, and I'll try to help get you going.
One thing that may not be documented clearly is that you have to restart cifs before the symlink.translations file is reloaded. Yes, it's a bug.
Mark Muhlestein -- mmm@netapp.com
<SNIP> -- End of excerpt from Raymond Brennan