-
Notifications
You must be signed in to change notification settings - Fork 399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scheduler should test for running agents before killing itself #48
Comments
Original Redmine Comment /etc/init.d/fossology stop |
Original Redmine Comment This is fixed with svn Changes the "stop" command from the use interface to wait till all currently executing agents have finished running before exiting the scheduler. Also added a new command: "die" that will cause the scheduler to kill all currently running agents then exit. Currently the GUI uses the "stop" command and does not offer the "die" command to the users. |
Original Redmine Comment Please update the test for this issue http://www.fossology.org/projects/fossology/wiki/Scheduler_Test_Cases#Scheduler-StartStop |
Original Redmine Comment added a test case for this. It can be found under src/scheduler/agent_tests/Functional/scheduler_testStop.php |
Original Redmine Comment Change unranked issues to rank 99 so they show up in a ranking report at the bottom. Otherwise, they show up on top. |
imported data with status resolved |
Author Name: Bob Gobeille
Original Redmine Issue: 681, http://www.fossology.org/issues/681
Original Date: 2012/02/01
Original Assignee: Alex Norton
Killing the scheduler kills all the running agents. I think we need to add a failsafe such as:
if there are running agents, the scheduler needs to tell the user and not do the kill. It should also tell the user to use the -f (see monk - full text license scanner #2 below) if the really want to force the kill.
add a new switch, like -f to force the scheduler to die (the current behavior).
add a new option to tell the scheduler to not schedule any new jobs and exit when the current ones are done. That is, just finish running the current jobs, email the user who requested this option, then exit.
The text was updated successfully, but these errors were encountered: