{"id":3262,"date":"2011-08-15T07:13:15","date_gmt":"2011-08-14T21:13:15","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=3262"},"modified":"2011-08-15T07:13:15","modified_gmt":"2011-08-14T21:13:15","slug":"basics-jobkill-goes-interactive","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2011\/08\/15\/basics-jobkill-goes-interactive\/","title":{"rendered":"Basics – Jobkill goes interactive"},"content":{"rendered":"

In a previous post<\/a>, I described how one could use jobquery<\/em> and jobkill<\/em> to terminate running scheduled clones in situations where NMC doesn’t allow the clone to be stopped from within the GUI. However, jobquery isn’t necessarily the most intuitive of interfaces if you’re not using it all the time.<\/p>\n

I was pleasantly surprised when I was preparing some documentation to note that jobkill, as of 7.6 SP2, has become interactive if there are multiple jobs running, which reduces the need to run jobquery if you’re wanting to just stop one scheduled operation.<\/p>\n

In 7.6 SP2, if you run jobkill without any arguments, and there are jobs running, you’ll run into an interactive session such as the following.<\/p>\n

# jobkill<\/strong>\n                      job id: 3104018;\n                        name: tara-5;\n                        type: savegroup job;\n                     command: ;\n           NW Client name\/id: ;\n                  start time: 1312763880;\n------------------------------------------------------\n                      job id: 3104025;\n                        name: \/d\/01;\n                        type: save job;tara.pmdg.lab\n                     command: \nsave -s tara.pmdg.lab -g nox-5 -LL -f - -m tara.pmdg.lab -t 1312026303 \n-l 5 -q -W 78 -N \/d\/01 \/d\/01;\n           NW Client name\/id: tara.pmdg.lab;\n                  start time: 1312763880;\n------------------------------------------------------\n                      job id: 3104026;\n                        name: \/;\n                        type: save job;\n                     command: \nsave -s tara.pmdg.lab -g nox-5 -LL -f - -m tara.pmdg.lab -t 1312026306 \n-l 5 -q -W 78 -N \/ \/;\n           NW Client name\/id: tara.pmdg.lab;\n                  start time: 1312763880;\n------------------------------------------------------\nSpecify jobid to kill ('q' to quit, 'r' to refresh): 3104018<\/strong>\nTerminating job 3104018\nSpecify jobid to kill ('q' to quit, 'r' to refresh): q<\/strong><\/pre>\n
So there you go \u2013 jobkill is interactive, helpful and now saves the hassle of running jobquery first.<\/p>\n","protected":false},"excerpt":{"rendered":"
In a previous post, I described how one could use jobquery and jobkill to terminate running scheduled clones in situations…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[6,16],"tags":[81,488,510,511],"class_list":["post-3262","post","type-post","status-publish","format-standard","hentry","category-basics","category-networker","tag-7-6-sp2","tag-interactive","tag-jobkill","tag-jobquery"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t