how about you set up one share that is user restricted ( only the account running the
build can use it ), and a second share open to all the developers.
when you are building, you close down the developer share, and when you are done, you
restore it.
---tom
*********** REPLY SEPARATOR ***********
On 10/4/2001 at 1:34 AM [EMAIL PROTECTED] wrote:
>From: Matthew Daly
>
>Sorry in advance if this message is munged. I'm an SMTP guy living in a
>Lotus Notes world.... =(
>
>The application that I'm working on is a distributed build environment
>where 8 machines are all mapping to the same share (on a central googlebyte
>drive) to compile umpteen thousand C++ projects per night. We're trying
>not to discourage the developers from using the files on this drive for
>debugging and stuff, but what invariably happens is that someone leaves
>Studio up overnight and the build fails because of my inability to
>overwrite files and directories that the developers have open. So I'd like
>to have a process that I could schedule to run, not just at the beginning
>of the 10-hour build, but throughout it in case someone sneaks in overnight
>and starts doing work in my sandbox.
>
>So, in a nutshell, I'd rather stay away from removing the share because the
>share is important to my machines too. It might turn out that just
>removing the open resources from unauthorized users would suffice for my
>purposes -- I just got fixed on the thought of disconnecting users ("In
>Use" or not) from shares because it's so easy to do that in Server Manager.
>
>BTW, Win32::Lanman is incredible! No doubt it's the same stuff going on
>under the hood, but much shorter and easier-to-read scripts that using
>Win32::OLE to talk to ADSI.
>
>-Matthew
>
>
>
>
>
>"Edward G. Orton" <[EMAIL PROTECTED]>@listserv.ActiveState.com on 10/01/2001
>12:46:32 AM
>
>Sent by: [EMAIL PROTECTED]
>
>
>To: <[EMAIL PROTECTED]>, "Perl-Win32-Admin Mailing List"
> <[EMAIL PROTECTED]>
>cc:
>Subject: Re: Stupid ADSI tricks
>
>
>----- Original Message -----
>From: <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, October 01, 2001 12:14 AM
>Subject: Stupid ADSI tricks
>
>
>> From: Matthew Daly
>>
>> So I've been endeavoring to disconnect (almost) all the users from a
>> sharepoint on a remote machine. In this quest, I'm indebted to Timothy
>> Jackson for pointing me toward ADSI. But I'm still not _quite_ able to
>get
>> to where I want.
>>
>> The problem is that I don't want to indisciminately end all the sessions
>> attached to this machine, just the ones that are associated with one
>> specific share. The script that I have come up with (included below)
>> checks all of the share's files that are open and disconnects only the
>> sessions of those file's "owners". But even this is blunt (to say
>nothing
>> of being s--l--o--w) because those sessions could be connected to other
>> shares that I don't want to touch. (Also, although I don't know how
>> important it is, it doesn't find users who are connected to the share but
>> don't have any open resources.)
>>
>> It seems like there must be a better way. One of the properties of the
>> share is the CurrentUserCount -- is there a way to identify which
>sessions
>> comprise that count? Also, is there a class finer than sessions so that
>I
>> can disconnect someone from a single share without affecting the rest of
>> the session or the rest of the share?
>>
>
>Why not just 'unshare' the share? This will force users to disconnect from
>the share, and yet not disrupt any other shares they are using. Once you do
>with it what you need, then you can share it again. Quick, clean, and
>relatively painless.
>
>ego
>Edward G. Orton, GWN Consultants Inc.
>Phone: 613-764-3186, Fax: 613-764-1721
>email: [EMAIL PROTECTED]
>> Thanks,
>> -Matthew
>> [EMAIL PROTECTED]
>
>
>_______________________________________________
>Perl-Win32-Admin mailing list
>[EMAIL PROTECTED]
>http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
>
>
>
>
>_______________________________________________
>Perl-Win32-Admin mailing list
>[EMAIL PROTECTED]
>http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
