But if the script is interacting with other programs, as many cronned scripts tend to do, it may not be able to find them. Also, I've had a bit of experience with Trustix, and have often found permissions problems in the site_perl directory - that is probably also worth checking.
But, as you said earlier, this is most likely not a libwww problem, so that's probably all the discussion we need. :) Ian On 7/17/02 1:44 PM, "Keary Suska" <[EMAIL PROTECTED]> wrote: > on 7/17/02 12:13 PM, [EMAIL PROTECTED] purportedly said: > >> If you're having a problem with running your scripts from cron, the answer >> is usually in your PATH environment variable or working directory - cron >> tends to run with different paths, and your script probably can't find >> libraries or other things it needs. > > Except that Perl does not rely on PATH and related variables to determine > module or loadable (.so) locations. The cron problem could be permissions or > a CWD problem which would effect finding custom modules, if that is even an > issue, or several other reasons. If there was some information about what is > going wrong, perhaps a more sensible solution could be presented. > >> On 7/17/02 12:28 PM, "Keary Suska" <[EMAIL PROTECTED]> wrote: >> >>> on 7/17/02 6:34 AM, [EMAIL PROTECTED] purportedly said: >>> >>>> Hi, I have a problem with LWP::UserAgent. As user root I can execute all my >>>> scripts, but if I use an other user or crontab (root) I can't execute them. >>>> My Distri is Trustix secure linux. I don't know where the bug is. My perl >>>> version is 5.0053 and the permissions are for all users the same. >
