Hello,
Not sure if the category "helpful Tip" is rightly choosen.
Anyway, that might benefits to "less advanced" programmers like me.
A few days ago I posted a question related to a fork issue on perl 5.8. I have just found the problem.
The script I quoted was using fork. At the begining of this script I was importing an other module with itself was calling an other module using fork in the definition subroutines: Schedule::Cron
Schedule::Cron was not installed on my other system running perl 5.005 (obviously as Schedule::Cron only works from version 5.6).
Commenting out the "use Schedule::Cron" solved my problem.
Now I still got a question for perl gurus:
-> In my script I was actually not using any reference to a Schedule::Cron function so how to explain this mess ?
Cheers,
U.
Not sure if the category "helpful Tip" is rightly choosen.
Anyway, that might benefits to "less advanced" programmers like me.
A few days ago I posted a question related to a fork issue on perl 5.8. I have just found the problem.
The script I quoted was using fork. At the begining of this script I was importing an other module with itself was calling an other module using fork in the definition subroutines: Schedule::Cron
Schedule::Cron was not installed on my other system running perl 5.005 (obviously as Schedule::Cron only works from version 5.6).
Commenting out the "use Schedule::Cron" solved my problem.
Now I still got a question for perl gurus:
-> In my script I was actually not using any reference to a Schedule::Cron function so how to explain this mess ?
Cheers,
U.
