Howdy.
So here's my trouble.
I've recently upgraded to the vMA 4.1 for my environment. I have several legacy scripts that I'm working on converting to pCLI when I've got time, but for now I need to get one of them running on the vMA. Part of the script invokes vmcontrol.pl for its operation.
When I run the script as user (vi-admin) or root, it works fine. When I put the scripts into a cron job, they fail. Logging from the job shows that in the cron environment the script is unable to compile the perl files and complains about finding a shared object file. My first thought is 'ah, permissions issue', but this doesn't seem to be holding true.
I know this is something obvious and easy, but I'm just not putting the dots together. I've tried forcing path variables into the cron, I've verified this across several users, and I've done this exact same process before on the 4.0 vMA plenty of times and it worked then. I know it's an environment thing, but I just don't have enough Fu to figure it out.
So I'm asking for help. Anyone have any ideas? All inputs (And I'm working on RTFM'ing, but I figured I'd work this thread at the same time) are appreciated.
Thanks!
- Abe
Integritas!
Abe Lister
Just some guy that loves to virtualize
==============================
Ain't gonna lie. I like points. If what I'm saying is something useful to you, consider sliding me some points for it!