Hello, Due to the fact that we have to purchase machine licenses rather than site licenses for Microsoft Office 97 we need to be able to limit which machine can run it from Win95 though samba. Any way to place restrictions on individual peices of software rather than having to ban machines from the entire samba program areas? regards Ben
On Thu, 6 Nov 1997 01:35:41 +1100, you wrote:>Hello, > >Due to the fact that we have to purchase machine licenses rather than site >licenses for Microsoft Office 97 we need to be able to limit which machine >can run it from Win95 though samba. Any way to place restrictions on >individual peices of software rather than having to ban machines from the >entire samba program areas? > >regards >Ben >Not without creating a seperate share for each aplication. However if each aplication is in it's own directory at the moment then you could create a simple script to generate the apropriate list of shares from a directory listing which you run when you install new software. You could even have an alias for your server (say 'apps') from which these shares are visible by using the 'netbios aliases=' and 'config file =/path/to/smb.conf.%L' parameters in your smb.conf. Host access can be restricted to specific shares using the 'allow hosts=' parameter.
On Thu, 6 Nov 1997, Ben B Hall wrote:> Hello, > > Due to the fact that we have to purchase machine licenses rather than site > licenses for Microsoft Office 97 we need to be able to limit which machine > can run it from Win95 though samba. Any way to place restrictions on > individual peices of software rather than having to ban machines from the > entire samba program areas?hi ben, ok, i think there's a feature in samba which limits the number of connections (users). there's no reason why you couldn't code up a per-share version of this (Connections[] array, referenced by cnum variables splattered all over the place. i think share connections are established by SMBtcon and SMBtconX, both of which call make_connection(). that might give you some starting places). this will end up looking a bit like NT: you can set "max number of connections" on a per-share basis. then, you install office in a specific share, and limit the number of users on it. luke <a href="mailto:lkcl@switchboard.net" > Luke Kenneth Casson Leighton </a> <a href="mailhost.cb1.com/~lkcl"> Lynx2.7-friendly Home Page </a> <br><b> "Apply the Laws of Nature to your environment because your environment applies the Laws of Nature to you" </b>