I'm looking to find a way to solve absolute symlinks created on a NFS automount and their resolution in CIFS.
I'm looking at the docs for Widelinks in Data ONTAP, and I can see where this could come in useful, but only if it somehow knows about all of the UNIX automount maps in an environment.
What I'm thinking is a script (perl) that would create a symlink.translations and cifsconfig_shares.cfg configuration based off of an automount map (or multiple automount maps). Has anybody seen something like this?
So it's output would generate something like:
automount map: auto.foo data1 filer1:/vol/vol1/data1 data2 filer2:/vol/vol2/data2
autofs: User creates a symlink in their homedir to /foo/data1 and /foo/data2: /home/user> ln -s /foo/data1 data1 /home/user> ln -s /foo/data2 data2
cifsconfig_share.cfg on filer1: cifs shares -add -widelink -vscan "foo_data1" "/vol/vol1/data1"
cifsconfig_share.cfg on filer2: cifs shares -add - widelink -vscan "foo_data2" "/vol/vol2/data2"
symlink.translations: Widelink /foo/data1/* \filer1\foo_data1* Widelink /foo/data2/* \filer2\foo_data2*
Thoughts: 1) Of course we would trust the automount maps! 2) All clients would have DFS support. 3) Hopefully, we don't do anything that would cause issues with share boundary checking. 4) Hopefully, we don't have issues with any special characters, etc. that are in the automount maps (we'll have to get rid of & wildcards). 4) We would be able to run this configuration on a change in the automount maps (perhaps in cron?)
If you've made it this far in my wandering and actually understand what's going on here, do you have any more thoughts? If so, please reply to me, and I will post a SUMMARY once I have an idea of what this will entail.
Thanks, Shawn
Shawn Stephens Sr. UNIX Systems Consultant stephenssh@saic.com The life of the creative man is lead, directed and controlled by boredom. Avoiding boredom is one of our most important purposes. - Saul Steinberg