Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Blue

SWIM's "at" requirement on Solaris

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?

4 REPLIES
Cisco Employee

Re: SWIM's "at" requirement on Solaris

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.

Blue

Re: SWIM's "at" requirement on Solaris

Can the LMS backup be converted to using JRM as well?

Cisco Employee

Re: SWIM's "at" requirement on Solaris

Not without some rearchitecting. It's not trivial.

Blue

Re: SWIM's "at" requirement on Solaris

155
Views
0
Helpful
4
Replies
CreatePlease to create content