If you make absolute links (beginning with a leading slash) you need to consider how the filer is going to resolve those since the UNIX exports and CIFS shares may be coming from different paths. The /etc/symlink.translations file is used to help the filer interpret absolute symbolic links.
If pchome is full of links to another directory on the filer and you use relative links you should be fine. You also need to enable symlinks with the cifs.symlinks.enable option.
/vol/vol0/pchome bob -> ../home_systems/bob jim -> ../home_software/jim
/vol/vol0/home_systems bob
/vol/vol0/home_software jim
Dennis Haag
-----Original Message----- From: Moshe Linzer [mailto:moshel@taux01.nsc.com] Sent: Wednesday, June 21, 2000 8:09 AM To: toasters@mathworks.com Cc: David.Lockwood@benettonformula.com Subject: Re: Filer (F740) with CIFS and NT Terminal Server Edition (Metaframe)
We are actually doing this slightly differently. The filer started out as pure Unix, so everything is using Unix security. When we added the Winframe servers (soon to move to TSE or Win2000), I found that I was able to make a CIFS Home directory on the filer:
options cifs.home_dir /pchomes
Then from the /pchomes directory, make symbolic links to the users actual (unix) home directory on the filer:
bob -> /homes_systems/bob jim -> /homes_software/jim
Now the user's home dir will be visible under TSE as \filer\userid (assuming the same userids on NT and Unix). You can setup the user's profile on TSE to mount this path automatically upon login. The beauty is that no unix home dirs have to be changed, and no additional mounts or automounts are needed.
Moshe
From owner-toasters@mathworks.com Wed Jun 21 14:52:50 2000 Date: Wed, 21 Jun 2000 10:57:00 +0100 From: "David Lockwood" David.Lockwood@benettonformula.com To: toasters@mathworks.com Subject: Filer (F740) with CIFS and NT Terminal Server Edition (Metaframe) Mime-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by smtp.mathworks.com id
FAA02894
Precedence: bulk
Has anybody had any experience using a filer with NT Terminal Server Edition
and Metaframe. I want to be able to have users UNIX (HP-UX 10.20) home directories on the filer and for the user to also be able to access that data from their Terminal Server (Metaframe 1.8) session.
For further information on Benetton Formula 1 visit our web site at
www.benettonf1.com. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please destroy and notify Benetton Formula on +44 1608678000.
----------------------------------------------------------------------------- Moshe Linzer | On the Internet, Unix Systems Manager | National Semiconductor, Israel | nobody knows you're a moron. Phone: 972-9-970-2247 | Fax: 972-9-970-2001 | - Network Magazine Email: moshel@nsc.com | -----------------------------------------------------------------------------
If you make absolute links (beginning with a leading slash) you need to consider how the filer is going to resolve those since the UNIX exports and CIFS shares may be coming from different paths. The /etc/symlink.translations file is used to help the filer interpret absolute symbolic links.
If pchome is full of links to another directory on the filer and you use relative links you should be fine. You also need to enable symlinks with the cifs.symlinks.enable option
/vol/vol0/pchome bob -> ../home_systems/bob jim -> ../home_software/jim
/vol/vol0/home_systems bob
/vol/vol0/home_software jim
Dennis Haag
The cifs.symlinks.enable option and the /etc/symlink.translations file aren't necessary here.
When you use the cifs.home_dir directory, you are implicitly defining a bunch of user shares. Essentially the cifs.home_dir directory and its contents is configuration data that is internal to the filer, and the filer understands symlinks.
The cifs.symlinks.enable option and the /etc/symlink.translations file are for handling the situation where a CIFS client tries to access a symlink. CIFS clients don't understand symlinks, so you must configure the filer to either 1) follow the symlink and return what the symlink refers to, or 2) deny access to the symlink.
Note that this is not an issue with NFS because the client follows the symlink, not the server. So when a NFS client accesses a symlink, the filer simply returns it. This is not possible with CIFS where the client does not understand what a symlink is.