To cause a program to run on another server, you'd need a protocol for doing that. Under NT, "Remote Cmd" (aka "RCmd") from the resource kit is not bad (rlogin and rsh from the resource kit are not good). If you installed the service on serverB, the service was running, you have rcmd.exe on serverA, and you are properly authenticated to serverB, then you could use:
But I won't go into this further because I don't think that is the best solution in this particular case.rcmd \\serverb path\test1.bat
When you run a program from Explorer, it usually runs the program with its default directory set to the directory where Explorer found the program. It sounds like just setting the default directory before running the program may fix your problem.
Now, you can't chdir('//serverB/directory$') because non-kernel processes on NT need a drive letter for their current directory. So you need to map a drive letter to that directory and chdir to the root directory of that drive. Win32::NetResource will let you map and unmap the drive letter.
I don't have Win32::NetResource examples handy or memorized so here is a non-Perl solution:
pushd \\serverB\directory$ test1.bat popd
In reply to RE: Re: External programs
by tye
in thread External programs
by clrobert
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |