SWIM's "at" requirement on Solaris

Unanswered Question
Jul 17th, 2009

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?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Fri, 07/17/2009 - 09:14

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.


This Discussion