Cron audit issue from running a Control-M job

francis · Post by **francis** » 14 Jul 2008 12:46

Hi, I'm troubleshooting a situation wherein a a cron audit failure results from a Control-M controlled script modifying a crontab file. Googling the issue, probable reasons are that the crontab has been edited from a non-SSH (i.e. telnet) or improper SSH implementation sessions.

http://www.derkeiler.com/Mailing-Lists/ ... /0019.html
http://www.sunmanagers.org/pipermail/su ... 06343.html

Q: How does Control-M connect to the agent machine? Is it possible to specify SSH as the connection protocol? How does an agent user switch to the job's owner id? Are there available options to control this?

Running under SunOS 5.8

Thanks.

hipikll · Post by **hipikll** » 14 Jul 2008 1:28

2) switch to other users - using 'su -' command
1) remote agent uses ssh protocol to connect to remote host