...
| Code Block |
|---|
[appadmin@someServer2 bin]$ /sbin/service grouperLoader restart Restarting Grouper loader: Grouper loader is running with processId: 2505, waiting for exit... Waiting for exit... Grouper loader is stopped Starting Grouper loader service... Grouper loader is running... done. [appadmin@lorenzo bin]$ ps -ef | grep gsh appadmin 30212 1 0 00:52 pts/0 00:00:00 /bin/sh /opt/appserv/tomcat_3b/webapps/grouperWs/WEB-INF/bin/gsh -loader appadmin 30213 30212 99 00:52 pts/0 00:00:12 /opt/appserv/java6/bin/java -Xms64m -Xmx750m -Dgrouper.home=/opt/appserv/tomcat_3b/webapps/grouperWs/WEB-INF/bin/../ -classpath /opt/appserv/tomcat_3b/webapps/grouperWs/WEB-INF/bin/../classes:/opt/appserv/tomcat_3b/webapps/grouperWs/WEB-INF/bin/../lib/*: edu.internet2.middleware.grouper.app.gsh.GrouperShellWrapper -loader appadmin 30232 29763 0 00:52 pts/0 00:00:00 grep gsh [appadmin@lorenzo bin]$ |
Note that as of Grouper 2.3, if you create a new loader job, you can have it scheduled without restarting the daemon by using an option in the New UI. If you're an admin of the group, under "More actions", there's an option named "Schedule loader process". This option can also be used if you change the loader's schedule.