James,
1. A Samba host is able to follow ALL symlinks, including those to automounter directories since it's a user level application, that uses the underline NFS client when needed. A filer is only an NFS server, thus it cannot follow symlinks like: /net/other_host 2. The filer has the /etc/symlink.translations feature, which lets you solve specific link needs. 3. You can use Samba as a workaround, but the better way to handle this is clean the past, and remove old links that are in no need when the data is centralized. As something that I've done in a real-life environment, you'll be amazed how many links-to-nowhere you currently have. By the way - this is a system-slower also, as many users often have long PATH variables that goes to many such non-existing non-existing directories.
Hope it helps, Eyal.
---------------------------------------------------------------------- eTraitel - I'm the new eBuzzword around !!! ---------------------------------------------------------------------- Eyal Traitel - Filer Escalation Engineer CNA, MCSE, CSA, NetApp CA
Network Appliance BV Holland Office Center Kruisweg 799b 2132 NG, Hoofddorp The Netherlands Office: +31 23 567 9685 Cellular: +31 6 5497 2568 Email: eyal@netapp.com ---------------------------------------------------------------------- Get answers NOW! - NetApp On the Web - http://now.netapp.com ----------------------------------------------------------------------
-----Original Message----- From: Coder, James (STP) [mailto:james.coder@guidant.com] Sent: Tuesday, January 09, 2001 4:00 PM To: toasters@mathworks.com Subject: following unix soft links
I recently moved users from a Solaris home server to our 760 (6.0.1.r1). filer. The users had created soft links (ln -s) to directories (either within their home directory or to other points via the automounter). Previously the Unix home shares were shared via samba and Unix users in the Windows environment could follow a soft link to the directory.
With the data moved to the NetApp, this is no longer available when using CIFS. I opened a case with NetApp and basically the answer was - that's right - the filer won't follow the link to a directory.
I have toyed with the idea of using samba on a box and letting the user point to it, thus letting samba provide the share service. Have not tried this, but was wondering if anyone has? Does anyone know of a work-around for this?
Thx in advance for any replies.
JCC
James C. Coder UNIX Administrator Guidant Corporation Phone: 651-582-4797 Email: james.coder@guidant.com mailto:james.coder@guidant.com