in reply to Re^2: The "Perl script on command line works but as cronjob it fails" story revisited
in thread The "Perl script on command line works but as cronjob it fails" story revisited

karlgoethebier:

In my (unfortunate) experience, clones are only identical the moment they're cloned. Normally there's an immediate tweak so they don't collide on the network. But soon after a package gets installed on one but not the other, or someone tweaks the "production" server and forgets to tweak the "backup" server. Or they make a test on the "backup" without cleaning up.

The long and short of it is that I no longer trust anyone's statements when they tell me the system is a "clone". That's the reason you need to check the environment, permissions, account setups, etc. for everything that matters to your code, or the code that your code relies on.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

  • Comment on Re^3: The "Perl script on command line works but as cronjob it fails" story revisited