From: Richard Lee
> ok so let's say on SERVERK, I cannot install any modules(no root
access
> and different compilers, gcc(I have tried perlgcc but to no success),
> and other
> reasons that I cannot explain nor understand and after numerous
> attempts(installing my own dir and others), I have gave up. Also since
> this is production machine
> which has other users using other things, any destruction behavior
would
> be catastrophic.
Never develop nor experiment on production systems. A mistake here could
wipe out your employer and result in criminal charges against you.
Step 1: Set up a clone of SERVERK to use as a development environment.
Step 2: Once this is done, if this is indeed an official project, get
the system admin to set up the correct tools and permissions on
the clone to build the application you need.
> so, what I am thinking of doing is,
>
> 1)on linux1, create a user dummyX whose initial .bashrc has immediate
> exit but do launch on perl script
> 2)perl script will go through SERVERK(if necessary) or go after
> server1-4... if it has connectivity. and run it's course.
>
> 3)so on SERVERK, user dummyY will launch a script called, launchX
> whose contents are
>
> ssh [EMAIL PROTECTED]
>
> Maybe this is stupid idea.. but I will try.
You will also need clones of the other production servers so you can
run your experiments without affecting any of the production equipment.
After you get it working, move just the final version to the production
systems and test them once again. You may still need to have the admin
install some additional tools and modules on the production systems.
Bob McConnell
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
