Return to Answer

added 2 characters in body

Source Link

edited Aug 4, 2022 at 19:22

Running Rscript from cron seems to have libPaths wrong - It seems to have other environment variables all toogether. This primarily messes up loading libraries. You can either install packages system-wide for R. Or use .libPaths().libPaths() at the start of the script, pointing it to where it should take the packages from.

Running Rscript from cron seems to have libPaths wrong - It seems to have other environment variables all toogether. This primarily messes up loading libraries. You can either install packages system-wide for R. Or use .libPaths() at the start of the script, pointing it to where it should take the packages from.

Running Rscript from cron seems to have libPaths wrong - It seems to have other environment variables all toogether. This primarily messes up loading libraries. You can either install packages system-wide for R. Or use .libPaths() at the start of the script, pointing it to where it should take the packages from.

Source Link

answered Aug 4, 2022 at 19:22

BlackNinja

Running Rscript from cron seems to have libPaths wrong - It seems to have other environment variables all toogether. This primarily messes up loading libraries. You can either install packages system-wide for R. Or use .libPaths() at the start of the script, pointing it to where it should take the packages from.