Let me add, real quick, that I'm trying to make this whole
process as transparent as possible to the Windows machines.
A member of the list made a very good suggestion to use
a service under NT to put a lock file on the share, but I
had failed to mention my desire for transparency on Windows.
To the windows machine, it should just look like the user
is editing a document on a windows-share.
Perhaps if I understood the methods Windows uses more, I
would know what to look for in the UNIX-Perl modules for a
solution?
Just kinda shootin' in the dark here...
>I'm writing a script that will allow our UNIX users to
>open Office Docs from their shell into a Windows session.
>The only big problem I'm running into is the communication
>between the UNIX perl script and Windows.
>
>How can the UNIX-side perl script know when the document
>is no longer being edited under UNIX?
>
>The user running the script is guaranteed to be the only
>one editing the doc. We use Samba on our UNIX machines
>to give access to these documents, and Samba has a prog
>that allows you to see which files are open, so I am going
>to use that, if you fine people don't have a better idea.
>
>Basically, the flow of this part of the UNIX-Perl script
>is supposed to go like so:
>
>(1) Check to see that Document is not being edited (RCS)
>(2) Copy to Samba-Shared Directory
>(1) Tell Windows to open Document
>(2) Wait for Document status to be "NOT OPEN"
>(3) If altered, copy changes to original Document
>(4) Release control of Document (RCS)
>
>Perhaps there is a way to use the same capabilities that
>Windows does to know if a document is being currently
>edited? If not, like I said, I'll just use the binary
>provided by Samba (though it's just so...messy...) ;>
>
>Thanks...
--
Aaron Rainwater
"I find that the harder I work,
the more luck I seem to have."
~ Thomas Jefferson
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
