Farid,
Have you considered our own "options cifs.home_dir" feature? This feature enables you to share automatically, in case you already have home directories that are called like the user.
Eyal.
You can take a look on the NOW site - http://now.netapp.com/Knowledgebase/solutionarea.asp?id=3.0.1796496.2595929 I'm also copying here more on the related feature/s -
=== cifs.home_dir Specifies the location of user home directories. The argument for the option is a comma-separated list of existing directory paths that are searched in order. If no list is supplied, the current list is displayed. The directories under these paths should have the names of users as their names. When a user connects to the filer using CIFS and there is a directory name that exactly matches the user's name, they will see a share with their name. That is their home directory. Only that user can access the home directory using this share. No other user can see that share name since other users are logged in under a different user name. The default value for this option is the null string. To set this option to the default value (a null string), use a pair of double quotes ("") as the argument.
cifs.home_dir_namestyle Specifies how the name portion of the path to a user's home directory is determined. If no argument is supplied, the current value of this option is displayed. Valid values for this option are: a null string, ntname, mapped, or domain. All user home directory paths begin with one of the paths given by the cifs.home_dir option, followed by a slash and the user's name. If this option is set to ntname then a user's Windows login name is used and only downward symlinks (in the directory hierarchy) are followed. If the value of this option is mapped then the user's UNIX name is used. The UNIX name is obtained by mapping the user's Windows login name using the file /etc/usermap.cfg. If this option is set to domain then the user's name includes both the user's domain and Windows login name separated by a slash. The default value for this option is the null string, which acts like ntname with the exception that symlinks are followed in any direction. To set this option to the defaul! t value (a null string), use a pair of double quotes ("") as the argument. ===
-----------------------------------------------------------------
eTraitel - I'm the new eBuzzword around !!!
-----------------------------------------------------------------
Get answers NOW! - NetApp On the Web - http://now.netapp.com
-----Original Message----- From: Farid Hamjavar [mailto:hamjavar@unm.edu] Sent: Wednesday, October 17, 2001 6:36 AM To: toasters@mathworks.com Subject: hello: CIFS shares and File Sharing Service
Greetings,
We're a fairly large enviromnet (unix). We have been using Netapp for a VERY long time. Authentication is done via unix NIS. Windows plays no role in any aspect of file-system or authentication management.
For past several years, we have been creating "CIFS Shares" as a means of "file sharing". We create NIS groups and our users (windows clients) login with their unix login/passwd and share files tamong themselves that way .... I know ... it's very basic.
Demand is increasing and we like to do something ...
1. is there any way that we can automate what we do already? i.e. is there a public-domain (or otherwise) software app that can automate our process of creating these "CIFS shares" in somewhat (more or less) they way we do it now?
2. Is there a reliable,reputable vendor (e.g. xdrive.com, of some sort, etc) that we can purchase their software and incorporate it into our existing Netapp infrastructure to implement filesharing (with CIFS or other methods) to offer to our users.
Any ideas for any of the above two methods can be very useful and greatly appreciated.
Thanks, Farid H. UNM-CIRT
On Tue, 16 Oct 2001, Traitel, Eyal wrote:
Date: Tue, 16 Oct 2001 22:53:43 -0700 From: "Traitel, Eyal" eyal@netapp.com To: Farid Hamjavar hamjavar@unm.edu, toasters@mathworks.com Subject: RE: hello: CIFS shares and File Sharing Service
Farid,
Have you considered our own "options cifs.home_dir" feature? This feature enables you to share automatically, in case you already have home directories that are called
like the user.
Eyal.
Thanks for reply.
We have had that for many years: Have been utilizing those features our users are able to map on the windows their unix home-dir....
I don't see that to be related [in any way] to the content of my original posting.
Farid UNM
You can take a look on the NOW site - http://now.netapp.com/Knowledgebase/solutionarea.asp?id=3.0.1796496.2595929 I'm also copying here more on the related feature/s -
=== cifs.home_dir Specifies the location of user home directories. The argument for the option is a comma-separated list of existing directory paths that are searched in order. If no list is supplied, the current list is displayed. The directories under these paths should have the names of users as their names. When a user connects to the filer using CIFS and there is a directory name that exactly matches the user's name, they will see a share with their name. That is their home directory. Only that user can access the home directory using this share. No other user can see that share name since other users are logged in under a different user name. The default value for this option is the null string. To set this option to the default value (a null string), use a pair of double quotes ("") as the argument.
cifs.home_dir_namestyle Specifies how the name portion of the path to a user's home directory is determined. If no argument is supplied, the current value of this option is displayed. Valid values for this option are: a null string, ntname, mapped, or domain. All user home directory paths begin with one of the paths given by the cifs.home_dir option, followed by a slash and the user's name. If this option is set to ntname then a user's Windows login name is used and only downward symlinks (in the directory hierarchy) are followed. If the value of this option is mapped then the user's UNIX name is used. The UNIX name is obtained by mapping the user's Windows login name using the file /etc/usermap.cfg. If this option is set to domain then the user's name includes both the user's domain and Windows login name separated by a slash. The default value for this option is the null string, which acts like ntname with the exception that symlinks are followed in any direction. To set this option to the defaul! t value (a null string), use a pair of double quotes ("") as the argument. ===
eTraitel - I'm the new eBuzzword around !!!
Get answers NOW! - NetApp On the Web - http://now.netapp.com
-----Original Message----- From: Farid Hamjavar [mailto:hamjavar@unm.edu] Sent: Wednesday, October 17, 2001 6:36 AM To: toasters@mathworks.com Subject: hello: CIFS shares and File Sharing Service
Greetings,
We're a fairly large enviromnet (unix). We have been using Netapp for a VERY long time. Authentication is done via unix NIS. Windows plays no role in any aspect of file-system or authentication management.
For past several years, we have been creating "CIFS Shares" as a means of "file sharing". We create NIS groups and our users (windows clients) login with their unix login/passwd and share files tamong themselves that way .... I know ... it's very basic.
Demand is increasing and we like to do something ...
is there any way that we can automate what we do already? i.e. is there a public-domain (or otherwise) software app that can automate our process of creating these "CIFS shares" in somewhat (more or less) they way we do it now?
Is there a reliable,reputable vendor (e.g. xdrive.com, of some sort, etc) that we can purchase their software and incorporate it into our existing Netapp infrastructure to implement filesharing (with CIFS or other methods) to offer to our users.
Any ideas for any of the above two methods can be very useful and greatly appreciated.
Thanks, Farid H. UNM-CIRT
-
Farid Hamjavar -
Traitel, Eyal