Future Work for CMT RM:

Since the current CMT RM MySQL database server is running on RHEL4 machine, as SLAC is stop supporting RHEL4 boxes, Arash will move the CMT RM database server to RHEL5/6 boxes. He will also update the MySQL server from version 4.1.22 to 5.x. After the new CMT RM MYSQL server is up and running, we have to made sure the following glastrm user cron job are working properly:

#CMT Release Manager
glastlnx20;1500 23 * * * * /u/gl/glast/infraCron/cron.pl >> ~/cron/log 2>&1

also for the glast user cron tab:

glastlnx20;1500 0 * * * * /u/gl/glast/infraCron/cron.pl >> ~/cron/log 2>&1
glastlnx02;1500 0 * * * * /u/gl/glast/infraCron/cron.pl >> ~/cron/log 2>&1
glastlnx03;1500 0 * * * * /u/gl/glast/infraCron/cron.pl >> ~/cron/log 2>&1

glastlnx20;1500 27 * * * * /u/gl/glastrm/grits-cpp/bin/lsfDaemon

One thing I think we can improve on CMT RM is to consolidate its multiple databases to one single database. There is no point to have only one single table in one single database. Also, there are so many databases, I don't even have access to all of them. I guess that is why we have SCON RM as improvement on these respect also.

  • No labels

1 Comment

  1. Rather than "crontab", Kim meant "trscrontab" above.  Note that trscrontab entries begin with <host>;<token-lifetime>, which is missing in standard crontabs.