samba - Oct 1997 - Win95 profiles on server (BUG#616)

>Looks like I was mistaken - there is no race condition as described.
>
>It would seem that the Win95 login routine doesn't start until after the
>preexec script has completed.  Presumed that the two processes would
>happen in parallel and that it was just a case of the server process being
>much quicker causing the .REG to be ready by the time the login script
>expects it.
That's right, there is no race condition. The mount of the share
can't complete till the preexec script has finished, which forces
the client to wait.
>Problem is I don't see how I could use something like 'max
connections >1' since that wouldn't limit me to one user at a time,
not one instance of
>each username at a time, correct?
Yes. "max connections" works on share names. So it will limit the
number of
people who can have that share name open at once.

You could be a little tricky and do this:

[%U]
	path = %H
	max connections = 1
	... other options ...


The [%U] gets substituted with their user name. It would mean that you 
automatically create a new share name for each user and these should
have independent connection limits.

I haven't actually tested this but it should work if the code
works as I think it does (ie. as I meant it to when I put it in!)

I think you could also do this with the [homes] share as long as the
users mounted \\server\user instead of \\server\homes. The above trick
just forces them to do this by creating a similar system to [homes]
but without the [homes] share.

Andrew

[hey, why has this been allocated a bug number - bug-tracking automation
interfering with your email to a non-bug-related thread? <G>]

On Thu, 9 Oct 1997, Andrew Tridgell wrote:
> That's right, there is no race condition. The mount of the share
> can't complete till the preexec script has finished, which forces
> the client to wait.
How does this work?  What is Win95 waiting for before it continues?  (I
ask without checking the source et al - you know it by heart surely!)
> [%U]
> 	path = %H
> 	max connections = 1
> 	... other options ...
> 
> 
> The [%U] gets substituted with their user name. It would mean that you 
> automatically create a new share name for each user and these should
> have independent connection limits.
Pretty damn cute, though if I wanted to do this I'd already be doing
using [homes] as you note - I really liked the convenience of always
having a fixed sharename for the user directory, since it allows me to
hard code paths for applications.  If I can't come up with a way to do
what I want, I expect I'll go back and user a [%U] share, and have the
preexec script generate a .REG file which the logon script imports - with
all the paths pointing to the correct share.

Is there any way I could make a preexec script that could deny the
connection?  Probably too late at that stage?   How about if a netlogon
preexec stopped the login process from progressing any further?

Any ideas?

Regards

---------------------------------------------------------------|-----|--
Louis Mandelstam              Tel +27 83 227-0712   Symphony  /|\   /|\
Linux systems integration     http://sr.co.za       Research {   } {   }
Johannesburg, South Africa    mailto:louis@sr.co.za (Pty)Ltd {___} {___}