in reply to Re^8: Perl app won't compile /run from cron
in thread Perl app won't compile /run from cron

Hi
I have been using perl for about 10 years. I struck and solved the cron PATH limited environment problem years ago.
Never had a problem running perl scripts from cron before.
Never new about @INC and never knew about or used local::lib. Never before needed to.

This has been a frustrating problem to solve. Now that I know what to search for, I find this is a problem shared by many others.
I am sure it would be really helpful for others in the future to add this as a specific item in the tutorials section of this website.


Dazz
  • Comment on Re^9: Perl app won't compile /run from cron

Replies are listed 'Best First'.
Re^10: Perl app won't compile /run from cron
by marto (Cardinal) on May 28, 2018 at 13:25 UTC

    "This has been a frustrating problem to solve."

    The issue had been explained to you several times, and your repeated response was that this was a bug, rather than you not taking the time to understand how things work.

    "I am sure it would be really helpful for others in the future to add this as a specific item in the tutorials section of this website."

    Your contribution would be welcome. Write something up.

[reply]
Re^10: Perl app won't compile /run from cron
by dazz (Beadle) on May 28, 2018 at 03:27 UTC
    Hi
    All of this was compounded by Chatterbox seemingly not working for me. I wasn't seeing the messages telling me I was posting duplicate posts, or that new replies had been posted, etc.
    When I pressed refresh to update Chatterbox, I didn't see that I had any replies. I now know that pressing refresh inadvertently generated duplicate posts. When people quite rightly complained about the duplicate posts, I couldn't see those messages either. I resorted to SuperSearch to finding replies. This appears to be because my message inbox was full.
    I have only just found the message inbox and cleared out some old messages. I note there is no link to a message inbox on the top right of the web pages, so it wasn't obvious to me that I had an inbox, and if I did, that there would be anything in it, so I had no reason to click the "Settings Nodelet>Message" link. Now Chatterbox is working I can see what's been happening.
    It was only after reading the messages that I figured out what a node reaper means and does. A reaper is a harvester so a message that says my node has been "harvested" doesn't tell me anything. NodeKiller I would have understood immediately.
    So if you have sensed a high level of frustration on my part, you'd be right. It's the reason visiting this website is the option of last resort for me. The information available from expert contributors here is fantastic. The website itself is not.

    Thank you for your tolerance and good information. I will try and stay away for as long as I can.

    Dazz
[reply]

      I've used this site for years and literally never experienced the problems you report. Front end wise this site is quite basic by modern standards. Perhaps you have altered some default browser settings, given the fundamental issues you seem to have getting updated content on your page and repeatedly resubmitting forms. NodeReaper on it's own would give some basic insight into what it's for. Reaped nodes explain who considered the node and why it should be reaped, e.g.. Also Tutorials->Understanding and Using PerlMonks.

[reply]

In Section Seekers of Perl Wisdom