07-17-2009 05:52 AM
In my neck of the woods, "casuser" has no cron access, i.e. it's neither in cron.allow nor cron.deny. That's supposedly why I cannot schedule LMS backups via the GUI. It's the same situation with "at". Then I came across this documentation:
"Software Management uses at and cron to schedule Software Management image transfers to devices. The process that performs the download is executed as casuser, so the user casuser must be allowed to use at and cron."
Well, SWIM has worked fine so far. How does it manage to get around the lack of at and cron access?
07-17-2009 09:14 AM
This is very old documentation. SWIM has been using JRM since RME 4.0. RME 3.5 used to use cron/at to schedule jobs.
07-17-2009 10:35 AM
Can the LMS backup be converted to using JRM as well?
07-17-2009 10:55 AM
Not without some rearchitecting. It's not trivial.
07-17-2009 10:41 AM
Here's one of the links on RME 4.0.5 that still claims "at" requirment for SWIM:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide