HP 1032 ClusterPack V2.4 Tutorial - Page 92

Kill a job in a queue, Using the Clusterware Pro V5.1 CLI, 8.8 Kill all jobs owned by a user

Get HP 1032 PDF manuals and user guides View all HP 1032 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 92 highlights

to the queue definition. The command or tool should be accessible and runnable on all nodes that the queue services. After adding, removing or modifying queues, it is necessary to reconfigure LSF to read the new queue information. This is done from the Management Server using the Clusterware Pro V5.1 CLI: % badmin reconfig Verify the queue has been modified by using the Clusterware Pro V5.1 CLI: % bqueues -l References: z 1.8.1 Add new Job Submission Queues Back to Top 1.8.7 Kill a job in a queue Using the Clusterware Pro V5.1 CLI: Jobs can be killed using the bkill command: % bkill Users can kill their own jobs. Queue administrators can kill jobs associated with a particular queue. References: z 3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface? Back to Top 1.8.8 Kill all jobs owned by a user Using the Clusterware Pro V5.1 CLI: All of a user's jobs can be killed by using the bkill on the special job id 0: % bkill -u 0

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
to the queue definition. The command or tool should be accessible and runnable on all nodes
that the queue services.
After adding, removing or modifying queues, it is necessary to reconfigure LSF to read the new
queue information. This is done from the Management Server using the Clusterware Pro V5.1
CLI:
%
badmin reconfig
Verify the queue has been modified by using the Clusterware Pro V5.1 CLI:
%
bqueues -l <queue_name>
References:
1.8.1 Add new Job Submission Queues
Back to Top
1.8.7 Kill a job in a queue
Using the Clusterware Pro V5.1 CLI:
Jobs can be killed using the bkill command:
%
bkill <jobid>
Users can kill their own jobs. Queue administrators can kill jobs associated with a particular
queue.
References:
3.7.9 How do I access the Clusterware Pro V5.1 Command Line Interface?
Back to Top
1.8.8 Kill all jobs owned by a user
Using the Clusterware Pro V5.1 CLI:
All of a user's jobs can be killed by using the bkill on the special job id 0:
%
bkill -u <username> 0