|Date: ||Tue, 8 May 2001 10:16:04 -0700|
|Sender: ||"SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>|
|From: ||"Karsten M. Self" <kmself@IX.NETCOM.COM>|
|Subject: ||Re: Was: SAS and Samba...again|
|In-Reply-To: ||<9d8r7n$hbvep$1@ID-75503.news.dfncis.de>; from magatz@YAHOO.COM
on Tue, May 08, 2001 at 03:05:04PM +0200|
|Content-Type: ||multipart/signed; micalg=pgp-sha1;
on Tue, May 08, 2001 at 03:05:04PM +0200, Andrea Magatti (magatz@YAHOO.COM) wrote:
> This time i'm trying to be more clear:
> The architecture "now":
> Compute Server: on a Sun Solaris server (E6500)
> Client: Win NT 4, using client SAS from a local File Server. that means:
> each time a client calls SAS.EXE
> this has to be retrieved from the local file server, the same appens for
> each DLL pointed by a SAS module (AF, GRAPH, EIS etc...). This way each
> client has a pure "SAS client installation".
> I would be pleased to know wheter:
> 1) can i put the SAS executable on a Samba network drive. This way i can
> point a logical drive to the Samba share on th Sun Solaris machine, avoiding
> this way to use the File Server (too busy for "real" file sharing)
> 2) has anyone tested this kind of architectural, with an heavy SAS
> application (AF developed) , with a lot of client server interaction ?
> Thanks in advance (first to Kasten....)
I don't see any reason it shouldn't work, you might want to just give it
You're already running SAS from a networked fileserver, Samba is pretty
much a functional equivalent for WinNT/2K in this regard. You're not
running SAS from the Solaris box, you're hosting it there. Though fnord
knows, the wrath of SAS/Legal may descend on you for this....
Any reason you can't just try (and report back the results)?
Karsten M. Self <firstname.lastname@example.org> http://kmself.home.netcom.com/
What part of "Gestalt" don't you understand? There is no K5 cabal