Hello!

    I am using ActiveState's ActivePerl on Windows NT 4 most of the
time.  I am not having a need of calling a Perl script on UNIX box from
my Perl script on my Windows NT machine.  The purpose is to FTP (upload)

a file from local machine to one of our server.  On the server, the
script will check for file duplication.  If the upload file's filename
has already been used, the current file with the same filename will be
renamed appending suffix (01, 02, etc.)

    The script on NT is simply a function to use NET::FTP to upload the
file to the server and call the script on the server to finish the
process.  Whereas, the main thing is, I don't know where to start for
the NT script to call the one on our UNIX server.

    Any help is appreciated!

--

***************************************

NetZero, Inc.

For remote jobs use Net::rexec

Alternatives to what you are trying to do:
1 - On the UNIX server run a scheduled job (CRON) to check for duplicate
files
2 - If NT has access to the Unix file system (NFS, SAMBA), have the NT
script check for duplicate files.

Cheers,
Adrian

Hypertech Pacific Group Taiwan
4F-1, #28, Lane 28, Hsing-Chung Rd.
Nankang, Taipei 115, Taiwan R.O.C.
tel: +886-2-2653 3922   fax: +886-2-2653 3920
web site: http://www.hypertech.com.tw
english company profile: http://www.hypertech.com.tw/ht_prf_c.htm

At work, we have several OpenBSD computers along with a bunch of Windows
based computers. Making a long story short, a specific activity on one of
the Windows computers will trigger a Perl script on one of the OpenBSD
computers. However, I used the KISS method. :) Samba is running on the
OpenBSD computer, and one of its shares is mapped as a network drive on the
Windows computer. A certain action on the Windows computer will cause it to
write a "semaphore" file on the OpenBSD's share. A background script
running on OpenBSD monitors the share for the existance of the semaphore
file, and will run a Perl script "if" so. It's a very easy way to do it.
Hope this gives you some ideas!

--

---------------------------
Dana Booth <dana[at]oz.net>
Tacoma, Wa., USA
---------------------------

Then again ,as yet another alternative to check for duplicates when
uploading files: use FTP ls and rename commands, so evertyhing can be
handled from the uploader's side.

Adrian

Hypertech Pacific Group Taiwan
4F-1, #28, Lane 28, Hsing-Chung Rd.
Nankang, Taipei 115, Taiwan R.O.C.
tel: +886-2-2653 3922   fax: +886-2-2653 3920
web site: http://www.hypertech.com.tw
english company profile: http://www.hypertech.com.tw/ht_prf_c.htm

With this method in mind, the script could be uploaded to the unix box via
ftp, then launched
by a cron job.  A semaphore file (the script itself perhaps) could be
removed to signal
completion of the script - no particular need exists to use either samba or
nfs.

If, however, the file to be uploaded is the one which must be renamed -
AND - it is guaranteed
that only the one win machine is uploading these files - it seems simplest
to script the entire process to run on the win box: Take a listing of the
upload directory.  Pipe the listing to a script which identifies and
resolves the file name conflict by renaming the file before uploading.
Upload the file with the new name to the BSD box.

Regards, Dennis Reichel